Grasp generation using a variational autoencoder

ABSTRACT

In at least one embodiment, a system determines a set of possible grasp poses that allow a robot to successfully grasp an object by generating a set of potential grasp poses, and then evaluating the performance of each potential grasp pose. In at least one embodiment, the system performs a refinement operation on the grasp poses, and based on an evaluation of the poses, creates an improved set of possible grasps for the object.

CLAIM OF PRIORITY

This application claims the benefit of U.S. Provisional Application No. 62/848,521 titled “Variational Grasp Generation,” filed May 15, 2019, the entire contents of which is incorporated herein by reference.

TECHNICAL FIELD

Embodiments described herein generally relate to the field of robotic control. In at least one embodiment, a machine learning system generates grasp poses that can be used by a robot to manipulate an object.

BACKGROUND

Robotic automation is an important field that, in various embodiments, enables increased productivity, safety, and economy when performing tasks. For robots that manipulate objects, generating grasp poses is often an important component of the task. In one example, a robot observes an object and determines where to position (a 3D position and 3D orientation also called a pose) a gripper so that the robot is able to pick up the object. The stability of an individual grasp may depend on the object and gripper geometry, object mass distribution, and surface frictions. The geometry around an object may impose additional constraints by limiting the grasp points that are reachable without causing the robot manipulator to collide with other objects in a scene. In some examples, this problem is approached by geometry-inspired heuristics to select promising grasp points around an object, possibly followed by a more in-depth geometric analysis of the stability and reachability of a sampled grasp. Many of these approaches rely on the availability of complete 3D models of an object, which can be a severe limitation in realistic scenarios where a robot only observes a scene with a noisy depth camera, for example. Therefore, improved methods of grasp determination are needed.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an example of a robotic system grasping various objects, in accordance with an embodiment;

FIG. 2 illustrates an example of an object to be grasped, in accordance with an embodiment;

FIG. 3 illustrates an example of predicted grasps for a mug, in accordance with an embodiment;

FIG. 4 illustrates an example of refined grasps for a mug, in accordance with an embodiment;

FIG. 5 illustrates an example of a grasp coordinate frame, in accordance with an embodiment;

FIG. 6 illustrates an example of a method of identifying a grasp pose, in accordance with an embodiment;

FIG. 7 illustrates an example of a process for training a system to identify grasp poses, in accordance with an embodiment;

FIG. 8 illustrates an example of refined grasp poses, in accordance with an embodiment;

FIG. 9 illustrates an example of training data generated with a physics simulator, in accordance with an embodiment;

FIG. 10 illustrates the effect of latent space dimensionality on success rate and coverage of the grasps, in accordance with an embodiment;

FIG. 11 illustrates the effect of number of refinement steps on improving the accuracy and coverage of generated grasps, in accordance with an embodiment;

FIG. 12 illustrates the effect of number of sampled grasps on coverage rate, in accordance with an embodiment;

FIG. 13 illustrates a table of grasp experiments of a variety of objects, in accordance with an embodiment;

FIG. 14 illustrates a tables of grasp experiment results, in accordance with an embodiment;

FIG. 15 illustrates an example of a process for training a system to identify grasp poses, in accordance with an embodiment;

FIG. 16A illustrates inference and/or training logic, according to at least one embodiment;

FIG. 16B illustrates inference and/or training logic, according to at least one embodiment;

FIG. 17 illustrates training and deployment of a neural network, according to at least one embodiment;

FIG. 18 illustrates an example data center system, according to at least one embodiment;

FIG. 19A illustrates an example of an autonomous vehicle, according to at least one embodiment;

FIG. 19B illustrates an example of camera locations and fields of view for the autonomous vehicle of FIG. 19A, according to at least one embodiment;

FIG. 19C is a block diagram illustrating an example system architecture for the autonomous vehicle of FIG. 19A, according to at least one embodiment;

FIG. 19D is a diagram illustrating a system for communication between cloud-based server(s) and the autonomous vehicle of FIG. 19A, according to at least one embodiment;

FIG. 20 is a block diagram illustrating a computer system, according to at least one embodiment;

FIG. 21 is a block diagram illustrating a computer system, according to at least one embodiment;

FIG. 22 illustrates a computer system, according to at least one embodiment;

FIG. 23 illustrates a computer system, according to at least one embodiment;

FIG. 24A illustrates a computer system, according to at least one embodiment;

FIG. 24B illustrates a computer system, according to at least one embodiment;

FIG. 24C illustrates a computer system, according to at least one embodiment;

FIG. 24D illustrates a computer system, according to at least one embodiment;

FIGS. 24E and 24F illustrate a shared programming model, according to at least one embodiment;

FIG. 25 illustrates exemplary integrated circuits and associated graphics processors, according to at least one embodiment;

FIGS. 26A and 26B illustrate exemplary integrated circuits and associated graphics processors, according to at least one embodiment;

FIGS. 27A and 27B illustrate additional exemplary graphics processor logic according to at least one embodiment;

FIG. 28 illustrates a computer system, according to at least one embodiment;

FIG. 29A illustrates a parallel processor, according to at least one embodiment;

FIG. 29B illustrates a partition unit, according to at least one embodiment;

FIG. 29C illustrates a processing cluster, according to at least one embodiment;

FIG. 29D illustrates a graphics multiprocessor, according to at least one embodiment;

FIG. 30 illustrates a multi-graphics processing unit (GPU) system, according to at least one embodiment;

FIG. 31 illustrates a graphics processor, according to at least one embodiment;

FIG. 32 is a block diagram illustrating a processor micro-architecture for a processor, according to at least one embodiment;

FIG. 33 illustrates a deep learning application processor, according to at least one embodiment;

FIG. 34 is a block diagram illustrating an example neuromorphic processor, according to at least one embodiment;

FIG. 35 illustrates at least portions of a graphics processor, according to one or more embodiments;

FIG. 36 illustrates at least portions of a graphics processor, according to one or more embodiments;

FIG. 37 illustrates at least portions of a graphics processor, according to one or more embodiments;

FIG. 38 is a block diagram of a graphics processing engine of a graphics processor in accordance with at least one embodiment;

FIG. 39 is a block diagram of at least portions of a graphics processor core, according to at least one embodiment;

FIGS. 40A and 40B illustrate thread execution logic including an array of processing elements of a graphics processor core according to at least one embodiment;

FIG. 41 illustrates a parallel processing unit (“PPU”), according to at least one embodiment;

FIG. 42 illustrates a general processing cluster (“GPC”), according to at least one embodiment;

FIG. 43 illustrates a memory partition unit of a parallel processing unit (“PPU”), according to at least one embodiment;

FIG. 44 illustrates a streaming multi-processor, according to at least one embodiment.

FIG. 45 is an example data flow diagram for an advanced computing pipeline, in accordance with at least one embodiment;

FIG. 46 is a system diagram for an example system for training, adapting, instantiating and deploying machine learning models in an advanced computing pipeline, in accordance with at least one embodiment;

FIG. 47 includes an example illustration of an advanced computing pipeline 4610A for processing imaging data, in accordance with at least one embodiment;

FIG. 48A includes an example data flow diagram of a virtual instrument supporting an ultrasound device, in accordance with at least one embodiment;

FIG. 48B includes an example data flow diagram of a virtual instrument supporting an CT scanner, in accordance with at least one embodiment;

FIG. 49A illustrates a data flow diagram for a process to train a machine learning model, in accordance with at least one embodiment; and

FIG. 49B is an example illustration of a client-server architecture to enhance annotation tools with pre-trained annotation models, in accordance with at least one embodiment.

DETAILED DESCRIPTION

The present document describes techniques that formulate the problem of grasp generation as sampling a set of grasps using a variational autoencoder and assessing and refining the sampled grasps using a grasp evaluator model. In at least one embodiment, both Grasp Sampler and Grasp Refinement networks take 3D point clouds observed by a depth camera as input. An evaluation of the approach is provided in simulation and real-world robot experiments. In an embodiment, the techniques described herein are shown to achieve 88% success rate on various commonly used objects with diverse appearances, scales, and weights. In at least one embodiment, the model is trained purely in simulation and works in the real world without any extra steps.

1. Introduction

Grasp selection is an important problem in robot manipulation. In at least one embodiment, a robot observes an object and an associated control computer system determines where to move the robot's gripper (3D position and 3D orientation) in order to pick up an object. For example, FIG. 1 illustrates a robotic system grasping various objects, in accordance with an embodiment. In at least one embodiment, a robot 102 having a gripper 104 is controlled by a computer system that implements the techniques described herein. In at least one embodiment, the robot 102 is able to perform improved grasps on various objects such as a cylinder 106, a box 108, or a bowl 110.

Grasp selection can be complex since the stability of grasps depends on object and gripper geometry, object mass distribution, and surface frictions. The geometry around an object may pose additional constraints on which grasp points are reachable without causing the robot manipulator to collide with other objects in a scene. FIG. 2 illustrates an example of an object to be grasped, in accordance with an embodiment. Various embodiments are described and tested on a variety of objects including a mug with a handle 202, a squeeze bottle 204, a cereal box 206, and a short box 208.

In some examples, this problem is approached by geometry-inspired heuristics to select promising grasp points around an object, optionally followed by a more in-depth geometric analysis of the stability and reachability of a sampled grasp. Many of these approaches rely on the availability of complete 3D models of an object, which may be a limitation in some realistic scenarios where a robot only observes a scene with a noisy depth camera, for example. To overcome this limitation, some embodiments move the camera to generate a full object model or perform shape completion, followed by geometry-based grasp analysis. However, in some examples, moving the camera might be impossible in constrained spaces, and shape completion might not be sufficiently accurate for grasp generation and evaluation.

In an embodiment, deep learning techniques are used to evaluate the quality of grasps from raw point cloud data. While, in some examples, this approach provides good grasp assessments, it still uses manually designed heuristics to sample grasps for evaluation or relies on blackbox optimization techniques such as the Cross Entropy Method (“CEM”). Additionally, it may not provide efficient means for improving sampled grasps. In at least one embodiment, we provide a learning-based framework for efficiently generating diverse sets of stable grasps for unknown objects. Various embodiments introduce two network architectures that sample, evaluate, and improve grasps.

At least one embodiment uses a variational auto-encoder (“VAE”) that can be trained to map the partial point cloud of an observed object to a diverse set of grasps for the object. In at least one embodiment, the VAE provides high coverage functioning grasps while generating only a relatively small number of failing grasps.

In at least one embodiment, to improve the precision of the VAE samples, techniques described herein utilize a grasp discriminator network that maps a point cloud of the observed object and the robot gripper to a quality assessment of the 6D gripper pose. In at least one embodiment, the gradient of this network can be used to improve grasp samples, for instance moving them out of collision or ensuring that the gripper is well aligned with the object.

Experiments demonstrate that the techniques described herein outperform other approaches and enable a robot to pick up 17 objects with a success rate of 88%, in an embodiment. Experimental results also show that various embodiments generate diverse sets of grasp samples while maintaining high success rate.

2. Alternative Embodiments

Learning 6-DOF Grasps. Some embodiments that solve the robot grasping problem are data-driven. Other embodiments are based on handcrafted feature vectors. Additional embodiments exploit convolutional architectures to operate on raw visual measurements. Many grasp-synthesis approaches are enabled by representing the grasp as an oriented rectangle in the image. This 3-DOF representation constrains the gripper pose to be parallel to the image plane. However, the drawbacks of such a representation may include the following: Since it limits the grasp diversity, picking up an object might be impossible given additional constraints imposed by the arm or task. In case of a static image sensor it may also lead to an excessively restricted workspace.

The techniques described herein, in various embodiments, address the problem of predicting the full 6-DOF pregrasp pose. This can be challenging due to occluded object parts that affect grasp success. Various embodiments circumvent this problem by including the auxiliary task of reconstructing the geometry of the target object. In at least one embodiment, the 6-DOF grasp outcome can be predicted using local geometry that is not part of the measurement. Various embodiments learn a grasp score function which is then used for grasp refinement.

Some examples formulate the problem as a regression to a single best grasp pose; however, such embodiments may inherently lack the ability to predict a diverse distribution of possible grasps. For example, one embodiment classifies 24 pre-defined orientations to choose a 6-DOF pre-grasp pose. Such a coarse resolution of SO(3) will necessarily lead to a limited diversity of the predicted grasps. In contrast, the grasp point detection method (“GPD”) uses a more dense sampling of candidate grasps: A point in the observed point cloud is sampled randomly and a Darboux frame is constructed which is aligned with the estimated surface normal and the local direction of the principal curvature. Although this heuristic creates a quite diverse set of candidate grasps, it may fail when generating grasps along thin structures such as rims of mugs, plates, or bowls since estimating those surface normals from noisy measurements is challenging. Various examples of the techniques described herein do not suffer from such bias. As a result, the techniques described herein are often able to find grasps where GPD is not able to.

Various embodiments formulate the grasping problem as a reinforcement learning problem or as approximations of it. The learned grasp policies are more expressive than describing only the final grasp pose. Still, the action space of many examples are usually se(2), limiting the diversity to top-down grasps.

Deep Neural Networks for Learning from 3D Data.

Various embodiments apply deep learning to 3D point cloud data. In some examples, 3D data are represented as 3D voxels or as extracted features from 2.5 depth images and processed using convolutional neural networks. For example, PointNet and PointNet++ are capable of representing the 3D data and extract the representation efficiently. Other examples use different variations of network architectures that represent 3D data, showing significant improvement on 3D object pose estimation, semantic segmentation, and part segmentation. In at least one embodiment, in order to estimate a successful gasp, the 6-DOF pose of the grasps needs to be accurate. In at least one embodiment, operating on a single RGB image does not provide the required accuracy since the input and output are not in the same domain. Therefore, various embodiments use 3D point cloud data to generate grasps. Some examples use PointNet++ for learning the representation to generate and evaluate grasps in SE(3).

Variational Autoencoders.

Variational autoencoders (“VAE”) are one category of deep generative models. VAEs can, in various examples, be trained in an unsupervised manner to maximize the likelihood of the training data. VAEs can been applied to a variety of tasks such as future prediction, generating novel view points and object segmentation. Various embodiments use a VAE to sample a diverse set of grasps in SE(3).

In at least one embodiment, the generator module is a VAE that is based on different samples from a latent space and the observed point cloud X The VAE generates different grasp proposals and the evaluation network (discriminator) accepts or rejects them based on how likely it is that each proposed grasp is successful. In at least one embodiment, both generator and discriminator take the 3D point cloud X of the object as part of the input.

3. 6-DOF Grasp Pose Generation

At least one embodiment formulates grasp pose generation as the process of producing sets of robot gripper poses such that closing the gripper at any of these poses results in a stable grasp of an object. Furthermore, in at least one embodiment, the process is designed to generate diverse sets of poses that ultimately cover all possible ways an object could be grasped. In at least one embodiment, robot gripper poses are given in SE(3), specifying the 3D translation and 3D orientation of the gripper. At least one embodiment focuses on generating grasp poses for single objects, and additional constraints due to a manipulator's reach and due to other objects in a scene are not considered and can be handled by manipulator trajectory optimization techniques. In some situations, grasp pose generation is challenging due to the narrow subspace of successful grasps in the space of all possible grasps, and small perturbations in the pose of a grasp can sometimes transform a successful grasp into a failure and vice versa. To generate diverse sets of stable grasps, at least one embodiment samples grasp poses using a variational autoencoder network followed by an iterative evaluation and refinement process. For at least one embodiment, the input to the embodiment is a point cloud of the object the robot should pick up.

At least one embodiment aims to learn the posterior distribution P(G*|X), where G* represents the space of all successful grasps and X is the partial point cloud of the object observed by a camera. In at least one embodiment, each grasp g∈G* is represented by (R,T)∈SE(3) where R∈SO(3) and T∈

³ are the rotation and translation of grasp g. In at least one embodiment, grasps are defined in the object reference frame, whose origin is X, the center of mass of the observed point cloud. In at least one embodiment, the axes are parallel to those of the camera frame as shown in FIG. 3 .

FIG. 3 illustrates an example of predicted grasps for a mug, in accordance with an embodiment. In at least one embodiment, a depth camera produces a point cloud, and elements of the point cloud correspond to objects such as a mug 302, a squeeze bottle 304, a cereal box 306, and a short box 308. In at least one embodiment, various grasps 310, 312, 314, and 316 are produced by the VAE.

As shown in FIG. 3 , the distribution of successful grasps G* can be complex and discontinuous. For example, the distribution of G* for a mug has multiple modes along the rim, handle, and bottom. In at least one embodiment, within each mode, the space of successful grasps is continuous but grasps of different modes can be separated from each other. In at least one embodiment, the total number of separate modes for each object category varies based on the shape and scale of objects.

In at least one embodiment, since the number of modes of G* is not known beforehand, various embodiments learn a generator module that maximizes the likelihood of successful grasps g∈G*. In at least one embodiment, since the generator only observes successful grasps during training, it is possible that the generator also generates failed grasps g∈G⁻. In at least one embodiment, in order to detect and refine these negative grasps, an evaluation module is trained to predict P(S|g, X), i.e., the probability of success for a grasp g and the observed point cloud X In at least one embodiment, applied to a sampled grasp, the evaluation module predicts grasp success and propagates the success gradient back through the network to generate an improved grasp pose. In at least one embodiment, this process is repeated. In at least one embodiment, discarding all grasps that remain below a threshold provides the final set of high quality grasps, an example of which is illustrated in FIG. 4 .

FIG. 4 illustrates an example of refined grasps for a mug, in accordance with an embodiment. In at least one embodiment, a depth camera produces a point cloud, and elements of the point cloud correspond to objects such as a mug 402, a squeeze bottle 404, a cereal box 406, and a short box 408. In at least one embodiment, refined grasps 410, 412, 414, and 416 are high quality grasps refined from the set of grasps produced by the VAE.

FIG. 5 illustrates an example of a grasp coordinate frame, in accordance with an embodiment. In at least one embodiment, a depth camera 504 is used to construct an object point cloud of a mug 502. In at least one embodiment, grasps are estimated with respect to the center of mass of the object point cloud, X. The axes of the grasp coordinate frame are parallel to those of the depth camera 504. In at least one embodiment, techniques described herein determine a set of high-quality grasps that allow a gripper 506 to grasp the mug successfully.

FIG. 6 illustrates an example of a method of identifying a grasp pose, in accordance with an embodiment. In at least one embodiment, an object point cloud X 602 is extracted from a depth image using plane fitting. In at least one embodiment, a Grasp Sampler Network 604 takes the point cloud and proposes different grasps 606. In at least one embodiment, an evaluator network 608 assesses the grasps 610 based on the object point cloud and the proposed grasp. In at least one embodiment, grasps are improved iteratively 612 using the gradient of the evaluator network.

3.1. Variational Grasp Sampler

FIG. 7 illustrates an example of a process for training a system to identify grasp poses, in accordance with an embodiment. The grasp sampler example shown in FIG. 7 is a generative model that maximizes P(G|X), the likelihood of a set of predefined successful grasps g∈G*. Given a point cloud X 708 and a latent variable z 710, the sampler is a deterministic function that predicts a grasp 712. In at least one embodiment, it is assumed that P(z), the probability density function of the latent space 710, is known and chosen beforehand. At least one embodiment uses P(z)=

(0, I). Given a point cloud X 708, different grasps are generated by sampling different z from P(z), in an embodiment. In at least one embodiment, the likelihood of the generated grasps can be written as follows: P(G|X)=∫P(G|X,z;Θ)P(z)dz  (1) Optimizing Eq. (1) for each positive grasp g∈G* requires integration over the values of the latent space, which is intractable. In order to make Eq. (1) tractable, an encoder Q(z|X, g) 702 maps each pair of point cloud X 708 and grasp g 706 to a small subspace in the latent space z 710. Given the sampled z˜Q, a decoder 704 reconstructs the grasp ĝ 712. In at least one embodiment, during training, the encoder 702 and decoder 704 are optimized to minimize the reconstruction loss

(g, ĝ) between ground truth grasps g∈G* and the reconstructed grasps ĝ. Furthermore, in at least one embodiment, the KL-divergence

_(K L) between the distribution Q(, |,) and the normal distribution

(0, I) is minimized to ensure a normal distributed latent space with unit variance. The loss function is defined as follows:

$\begin{matrix} {\mathcal{L}_{vae} = {{\sum\limits_{{z \sim \mathcal{Q}},{g \sim G^{*}}}{\mathcal{L}\left( {\hat{g},g} \right)}} - {{\alpha\mathcal{D}}_{KL}\left\lbrack \left( {{\mathcal{Q}\left( {{{\mathcal{z}}❘X},g} \right)},{\mathcal{N}\left( {0,I} \right)}} \right. \right.}}} & (2) \end{matrix}$ In at least one embodiment, Eq. (2) is optimized using stochastic gradient descent. In at least one embodiment, for each mini-batch, the point cloud X is sampled for an object observed from a random viewpoint. In at least one embodiment, for the sampled point cloud X, grasps g are sampled from the set of ground truth grasps G* using stratified sampling. To combine the orientation and translation loss, at least one embodiment defines the reconstruction loss as follows:

$\begin{matrix} {{\mathcal{L}\left( {\hat{g},g} \right)} = {\frac{1}{n}\Sigma{{{\mathcal{T}\left( {g;p} \right)} - {\mathcal{T}\left( {\hat{g};p} \right)}}}_{1}}} & (3) \end{matrix}$ where

(⋅; p) is the transformation of a set of predefined points p on the robot gripper. In at least one embodiment, during training, the decoder 704 learns to decode the latent value z that is sampled from

(0, I) and generates grasps while the encoder 702 learns to output z such that it contains enough information to reconstruct the grasp pose while maintaining the normal distribution. In at least one embodiment, during inference, the encoder Q is removed and latent values are sampled from

(0, I).

In at least one embodiment, in this encoder and decoder architecture, each point has a 3D coordinate and a feature vector. In at least one embodiment, the features at each layer are computed based on the features of each point and the 3D relation of the points with respect to each other. In at least one embodiment, the features of each input point x∈X are concatenated to g=[R,T]. In at least one embodiment, in the decoder 704, each point feature is concatenated with the latent variable z. In at least one embodiment, the encoder 702 learns to compress the relative information of point cloud X and latent variable grasp g in such a way that it can be reconstructed by the decoder 704.

3.2. Grasp Pose Evaluation

In at least one embodiment, the grasp sampler trains the continuous posterior distribution P(G|X, z) using only positive grasps. As a result, various embodiments might contain failed grasps that are in between the modes of the distribution. In at least one embodiment, these transitional grasps and other false positives are identified and pruned out. To do so, such embodiments use a grasp evaluation network that assigns a probability of success P(S|g, X) to each grasp. In at least one embodiment, this network needs reasons about grasps relative to the observed point cloud X, and also is able to extrapolate to unobserved parts of the object. Some embodiments learn to classify grasps based only on local observed parts of an object. In some examples, the observed point cloud of an object has imperfections such as missing or noisy depth values. To mitigate this problem, previous methods may resort to use high quality depth sensors or using multiple views which limits the deployment of the system outside of controlled environments. Various embodiments classify each grasp using only the imperfect observed point cloud X of the object.

In at least one embodiment, success of a grasp pose depends on the relative pose of the grasp with respect to the object. In at least one embodiment, the inputs to the evaluator network are point cloud X and grasp g. Similar to the Grasp Sampler, at least one embodiment uses the PointNet architecture for the Grasp Evaluator. There are multiple ways for classifying grasps. At least on embodiment associates the 6D pose of the grasp g to the features of each point x∈X in the first layer. Experiments show that such a representation may lead to poor accuracy in grasp classification, in some examples. At least one embodiment represents a grasp g in a way more closely tied to the object point cloud: the robot gripper is approximated by a point cloud, X_(g), rendered according to the 6D grasp pose g. The object point cloud X and gripper point cloud X_(g) can be combined into a single point cloud by using an extra binary feature that indicates whether a point belongs to the object or to the gripper. In the PointNet architecture, the features for each point can be functions of features of the point itself and its neighbors plus the relative spatial relation of the points. Using the unified point cloud X∪X_(g) allows the relative information between grasp pose g and object point cloud X to be used for classifying the grasps. In at least one embodiment, the grasp evaluator is optimized using the crossentropy loss by optimizing

_(evaluator)=−(y log(s)+(1−y)log(1−s))  (4) where y is the ground truth binary label of the grasps indicating whether the grasp is successful or not and s is the predicted probability of success by the evaluator.

In at least one embodiment, in order to train a robust evaluator, the model is trained with both positive and negative grasps. In at least one embodiment, since the space of all possible 6D grasp poses is combinatorially large, it is difficult to sample all the negative grasps. Instead, some embodiments do hard negative mining to sample negative grasps. In at least one embodiment, the set of hard negative grasps G⁻ is defined as the grasps that have similar pose to a positive grasp but that are either in collision with the object or are too far from the object to grasp the object. More formally G⁻ is defined as: G ⁻ ={g ⁻ |∃g∈G*:

(g,g ⁻)<∈}  (5) where

(⋅,⋅) is defined in Eq. (3). In at least one embodiment, during training, g⁻ is sampled from a set of pre-generated negative grasps and by randomly perturbing positive grasps to make the mesh of the gripper either collide with the object mesh or to move the gripper mesh far from the object.

3.3. Iterative Grasp Pose Refinement

In at least one embodiment, although the evaluation network rejects implausible grasps, a large portion of the rejected grasps can be close to successful ones. In at least one embodiment, this insight is exploited by searching for a transformation Δg∈SE(3) that turns an unsuccessful grasp into a successful one. In at least one embodiment, the system looks for a refining transformation Δg that increases the probability of success, i.e., P(s=1|g+Δg)>P(s=1|g). In at least one embodiment, the evaluation network represents a differentiable function of success s based on the point cloud X and grasp g. In at least one embodiment, the refinement transformation that leads to enhanced improvement in success probability can be computed by taking the derivative of success with respect to the grasp transformation: ∂S/∂g. In at least one embodiment, the partial derivative ∂S/∂g provides the transformation for each point in the gripper point cloud X_(g) so as to increase the probability of success. In at least one embodiment, since the derivative is computed with respect to each point on the gripper independently, it can lead to non-rigid transformations for X_(g). In at least one embodiment, to enforce the rigidity constraint, the transformed gripper point cloud X_(g) is defined as a function of orientation of the grasp defined in Euler angles R_(g)=(α_(g), β_(g), γ_(g)) and translation T_(g). Using the chain rule, Δ_(g) is computed as follows:

$\begin{matrix} {\Delta_{g} = {\frac{\partial S}{\partial g} = {\eta \times \frac{\partial S}{\partial{\mathcal{T}\left( {g;p} \right)}} \times \frac{\partial{\mathcal{T}\left( {g;p} \right)}}{\partial g}}}} & (6) \end{matrix}$

In at least one embodiment, since the partial derivative ∂S/∂g is only a valid approximation in the local neighborhood, we use hyper-parameter η to limit the magnitude of updates at each step. In at least one embodiment, the system chooses η in such a way that the maximum translation update of the grasp does not exceed 1 cm. FIG. 8 shows the refinement of estimated grasps at different iterations. In at least one embodiment, the system produces a set of refined poses 806 that can be used to grasp the bowl 802.

FIG. 8 illustrates an example of refined grasp poses, in accordance with an embodiment. In at least one embodiment, a bowl 802 is scanned by using a depth camera. A depth camera can be any device that provides an image with depth information for at least part of the image. For example, a depth camera can be a binocular camera, a radar imaging system, or a laser imaging system such as LIDAR. In at least one embodiment, image data provided by the depth camera is used to generate a point cloud 804 of the bowl 802.

4. Experiments

Training Data for Grasping.

To generate reference sets of successful grasps, various embodiments use the physics simulation FleX, which provides realistic simulation of grasps for arbitrary object shapes. In at least one embodiment, candidate grasps are sampled based on the object geometry. Various embodiments sample random points on the object mesh surface and align the gripper's z-axis (see FIG. 5 ) with the surface normal. In at least one embodiment, the distance between the gripper and the object surface is sampled uniformly between zero and the gripper's finger length. In at least one embodiment, the orientation around the z-axis is also drawn from a uniform distribution. At least one embodiment only simulates grasps that are not in collision and whose closing volume between the fingers intersects the object. Experiments described herein use 206 objects from six categories in ShapeNet: boxes and cylinders (randomly generated), as well as bowls, bottles and mugs. A total of 10,816,720 candidate grasps are sampled of which 7,074,038 (65.4%) are simulated, i.e., those that pass the non-empty closing volume test. In at least one embodiment, the simulation comprises a free-floating parallel jaw gripper and the free-floating object without gravity. In various examples, surface friction and object density are kept constant. In at least one embodiment, after closing its fingers the gripper executes a predefined shaking motion. In at least one embodiment, a grasp is labeled successful if the object is kept between both fingers. Overall, in at least one example, we generate 2,104,894 successful grasps (19.4%). The resulting positive grasp labels are densely distributed as shown in the examples in FIG. 9 . In at least one embodiment, points of a point cloud 906 represent successful grasps of a bowl 902 by a gripper 904.

Training.

In at least one embodiment, both grasp generator and evaluator networks are using PointNet++ and have similar architectures. In at least one embodiment, both modules consist of three set-abstraction layers followed by fully connected layers. In at least one embodiment, each batch of the training data for the generator network consists of a rendering of the object from a random view and 64 grasps that are sampled using stratified sampling to make sure the sampled grasps have enough diversity. In at least one embodiment, the weight for KL-Divergence loss (α in Eq. (2)) is set to 0.01. In at least one embodiment, each batch of training data for the evaluator network consists of 30% positive, 30% negative grasps, and 40% hard negative grasps. In at least one embodiment, hard negative grasps are selected from perturbed positive grasps by applying ±0.6 radians in each axis and ±3 cm to translation. In at least one embodiment, both models are trained with the Adam optimizer using a learning rate of 0.0001. In at least one embodiment, the grasps are generated in simulation and no real data is used to train the models.

Network Architecture Details.

In at least one embodiment, both grasp generator and evaluator are based on PointNet++ architecture. In at least one embodiment, both models include three set abstraction layers. In at least one embodiment, each set abstraction layer samples 128, 32, and all the points. In at least one embodiment, each set abstraction layer samples the points that are within 2 cm, 4 cm, ∞ and radius of the sampled points. In at least one embodiment, each set abstraction layer uses 3 fully connected layers to compute the features. In at least one embodiment, the number of channels for each set abstraction layer are [64, 64, 128], [128, 128, 256] and [256, 256, 512] respectively. In at least one embodiment, the set abstraction layers are followed by two fully connected layers with 1024 units. In at least one embodiment, the grasp generator network outputs a rotation R that is represented as unit quaternion and a translation T. In at least one embodiment, quaternions are generated by applying L2-Norm on a linear fully connected layer. In at least one embodiment, no normalization is done for the translation T. In at least one embodiment, the evaluator network predicts the score for each grasp using a softmax layer.

Evaluation Metrics.

At least one embodiment uses two metrics to quantitatively evaluate grasping methods: success rate and coverage rate. Success rate is the ratio of successful grasps among all predicted grasps. In at least one embodiment, this metric considers the grasp that is executed and does not contain information about the other grasps. In at least one embodiment, predicting only one grasp is not suitable for 3D grasping, because the predicted grasp may lead to collision of the robot with other objects in the environment or there may not be any possible valid robot joint configuration that can reach the predicted grasp. In order to achieve an executable successful grasp, various embodiments generate a diverse set of grasps from different translations and directions to check for kinematic feasibility and collision avoidance. As a result, some embodiments introduce the coverage rate which captures the diversity of the grasps and measures how well the space of positive grasps G* is covered by the generated grasps. In at least one embodiment, a positive grasp g∈G* is covered by the set of predicted grasps, Ĝ, if there exists a grasp ĝ∈Ĝ that is at most 2 cm away from the grasp g. In many situations, positive grasps that have similar translation in object frame have similar orientation. As a result, at least one embodiment uses the distance in translation of the grasps as the criteria for evaluating whether a grasp is covered or not. Since grasps are defined in SE(3), G* is uncountably infinite. As a result, for some embodiments, G* is approximated by sampling grasps while generating data. Success rate and coverage rate are analogous to precision and recall in the context of binary classification. Similar to precision-recall curves, some embodiments use the curves of success rate and coverage rate for analyzing and evaluating the techniques described herein. Some examples use the AUC of success-coverage rate for ablation studies and analysis.

4.1. Analysis and Ablation Studies

The present document evaluates the effect of different parameters and modules quantitatively using the same physics simulation as in the generation of training data. In ablation studies, 86 object point cloud observations are generated for 10 different objects that are held out during training. For each point cloud, 200 latent values are sampled and refined over 10 iterations, resulting in 2200 grasps per view point and 182,600 grasps in total.

Dimensionality of the Latent Space.

In various examples, there is an inherent tension when deciding the dimensionality of the latent space which affects the quality of the generated grasps. In many situations, the latent space needs to have enough capacity to allow the VAE to reconstruct the grasps while, at the same time, a high-dimensional latent space leads to over-fitting and requires significantly more training data to be covered. In various examples, it also deteriorates the quality of sampled grasps during inference, especially when the sampled latent values during inference are not seen by the generator network during training. To analyze this effect, the generator network can be evaluated with increasing numbers of dimensions for the latent space. FIG. 10 illustrates the effect of latent space dimensionality on success rate and coverage of the grasps, in accordance with an embodiment.

As can be seen in various examples, a dimensionality of one has a low AUC because the latent space does not have enough capacity. In at least one embodiment, although 3-dimensional and 4-dimensional latent spaces lead to a slightly better

_(vae) on the training data, they perform worse during inference because the VAE cannot cover the latent space densely during training. Given these results, a two-dimensional latent space is used for subsequent evaluations.

Effect of Refinement on Grasp Quality.

While the grasp refinement increases the probability of success based on the evaluator network, it does not necessarily mean that the refined grasps succeed during test time. To analyze the actual improvement induced by each refinement step, we evaluate the grasps in simulation. FIG. 11 illustrates the effect of number of refinement steps on improving the accuracy and coverage of generated grasps, in accordance with an embodiment. In the example shown, not only does the success rate of the generated grasps increase, the coverage rate increases as well. This is because when grasps are improved they get closer to the sampled positive grasps in G*. The AUC of the curves plateaus after the 10th iteration of refinement.

Effect of Sampled Grasps on Coverage.

In previous sections, ablation studies using 200 random latents were conducted because that was the maximum batch size that fits in GPU memory and it is the same setting that was used for robot experiments. Since the number of sampled latents was limited, the coverage rate in FIG. 11 was less than 0.5 even after 10 refinement steps. In order to demonstrate how the number of sampled grasps affect the coverage, 2000 grasps were sampled in 10 different batches on the same point clouds that were used in previous ablation studies. FIG. 12 illustrates the effect of number of sampled grasps on coverage rate, in accordance with an embodiment.

4.2. Robot Experiments

The ultimate test of the generated grasps is to execute them in the real world and deal with imperfect perception, robot joint limits, control errors, and physical phenomena such as friction that are difficult to model. We show that in at least one embodiment: (1) the techniques described herein scale to the real world despite being trained purely in simulation; (2) the generated grasp distribution is diverse enough to find successful grasps even after discarding those that violate robot kinematics and collision constraints; (3) the method's diverse grasp sampling leads to higher success rate in comparison to an alternative 6-DOF grasp planner (“GPD”).

Experiments were done using a 7-DOF Franka Panda manipulator with an Intel Real Sense D415 camera mounted on its parallel-jaw gripper. A set of commonly-used objects that are challenging visually and physically were used. The weights of the chosen objects were between 42 g (pepper shaker) and 618 g (mustard bottle).

Protocol.

Each object was placed in three different stable poses on a table in front of the robot. The robot's end-effector was moved such that the hand-mounted depth camera has an unobstructed view of the table top. A grasp was considered successful if the robot could lift the object 10 cm without dropping it.

The measured point cloud was filtered, the table plane was removed and the remaining points were clustered. The extracted object point cloud served as an input to the method and also for GPD. Both methods returned a list of scored grasps. A motion planner was used to check for a collision-free path to each grasp pose and the one with the highest score was executed. If no grasp in the returned set could be executed, the trial was considered a failure. In total, 51 trials per method were run.

Results.

FIG. 13 illustrates a table of grasp experiments of a variety of objects, in accordance with an embodiment. Table 1 of FIG. 13 shows that the techniques described herein outperform GPD on success rate across all objects tested, in an embodiment. One of the reasons is that the method generates diverse grasps, which facilitates finding kinematically feasible ones. In contrast, GPD does not generate many different grasps which sometimes leads to situations in which no kinematically feasible grasp can be found. Mugs are particularly difficult for GPD because it does not generate any grasps from the rim. For some embodiments, another source of problems comes from the grasps where the finger gripper is tangent to one of the surfaces of the object. In these cases, a slight error in executing the grasp can change the grasp from grabbing the object to pushing it. FIG. 14 illustrates a table of grasp experiment results, in accordance with an embodiment.

5. Additional Features

In this document, 6-DOF GraspNet is described that generates diverse sets of grasps for unknown objects, in various examples. In various embodiments, the method includes a trained VAE that samples a variety of grasps for an object. While the VAE is able to capture the complex distributions of successful grasp poses, various examples do not quite provide the accuracy required for highly robust grasp generation. To overcome this limitation, at least one embodiment additionally introduces a grasp evaluator network that assesses grasp quality and refines grasps in an iterative process.

In at least one embodiment, the training of the model is done using synthetic grasp data generated by a physics simulator. Therefore, various embodiments of the model can scale to large sets of objects without requiring to collect any data in the real world. Experiments described herein show that at least one embodiment can transfer to the real world on objects with unknown 3D models by deploying the method on a real robot platform and an on-board RGB-D camera. Robot experiments were performed on 17 objects with unknown 3D models and achieved state-of-the-art results in 3D grasping. An analysis of the generated grasps in terms of success rate and coverage was conducted via ablation studies in a realistic physics simulator.

In at least one embodiment, all the latent values are sampled uniformly and then grasps are removed based on collision checks and kinematically feasible solutions. In various embodiments, the sampler or the evaluator may be trained in a way that not only considers the object of interest but also considers the surrounding objects to directly avoid generating colliding or infeasible grasps. Other examples use the evaluator not only to refine sampled grasps but to provide real-time feedback guidance for a manipulator approaching an object. Experiments described herein provide evidence that at least one embodiment of a gradient-based approach succeeds in moving a manipulator closer to a successful grasp.

FIG. 15 illustrates an example of a process for training a system to identify grasp poses, in accordance with an embodiment. In at least one embodiment, a computer system such as the one of the computer systems described and illustrated in FIGS. 16-49 , executes instructions stored in a computer-readable memory that cause the computer system to perform the operations shown and described in FIG. 15 .

In at least one embodiment, the process begins at block 1502 with the computer system obtaining 3D image information for an object. In at least one embodiment, 3D image data is obtained from one or more depth cameras. In at least one embodiment, 3D image data may be collected with various 3D imaging devices such as a RADAR, LIDAR, CT scanner, MRI imager, ultrasound, or x-ray machine. In at least one embodiment, the device used to collect the 3D image data produces a point cloud. In other examples, the 3D image data produced by the 3D imaging device is converted to a point cloud at block 1504. In at least one embodiment, other types of 3D imaged data may be used directly by the generation and evaluation network to generate and evaluate grasp poses.

In at least one embodiment, at block 1506, the computer system provides the point cloud (or other 3D image data) to an autoencoder, which generates a set of grasp poses for the object. In at least one embodiment, the autoencoder is trained to produce grasp poses for the particular type of object and a particular type of robot. In at least one embodiment, at block 1508, the computer system uses another autoencoder (sometimes called the evaluation network) to quantify the quality of each generated grasp pose. In at least one embodiment, the evaluation network takes the point cloud and the grasp pose to be evaluated as input, and produces a measure of the quality of the grasp. In at least one embodiment, the measure is a probability that the grasp pose will succeed, where success is measured by the chance that the grasp will allow performance of a defined object-manipulation task. In at least one embodiment, the measure is an proportional indication of grasp security. In at least one embodiment, the evaluation network provides a differentiable measure of the quality of the grasp.

In at least one embodiment, at block 1510, the computer system uses the evaluation network to refine each of the generated grasps by determining a gradient for each pose, and adjusting each pose to a refined grasp based on the gradient. In at least one embodiment, the grasp pose is refined as illustrated in described above in FIG. 7 and the associated description. In at least one embodiment, grasp poses are refined iteratively. In at least one embodiment, at decision block 1512, the computer system determines if additional refinement is desired, and if so, execution returns to block 1508 where the refined grasp is evaluated and further refined based on a gradient for the refined grasp. In at least one embodiment, if the grasp is sufficiently refined, executed advances to block 1514 and the refined grasp is used to direct a robot to grasp the object.

Inference and Training Logic

FIG. 16A illustrates inference and/or training logic 1615 used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided below in conjunction with FIGS. 16A and/or 16B.

In at least one embodiment, inference and/or training logic 1615 may include, without limitation, code and/or data storage 1601 to store forward and/or output weight and/or input/output data, and/or other parameters to configure neurons or layers of a neural network trained and/or used for inferencing in aspects of one or more embodiments. In at least one embodiment, training logic 1615 may include, or be coupled to code and/or data storage 1601 to store graph code or other software to control timing and/or order, in which weight and/or other parameter information is to be loaded to configure, logic, including integer and/or floating point units (collectively, arithmetic logic units (ALUs)). In at least one embodiment, code, such as graph code, loads weight or other parameter information into processor ALUs based on an architecture of a neural network to which such code corresponds. In at least one embodiment code and/or data storage 1601 stores weight parameters and/or input/output data of each layer of a neural network trained or used in conjunction with one or more embodiments during forward propagation of input/output data and/or weight parameters during training and/or inferencing using aspects of one or more embodiments. In at least one embodiment, any portion of code and/or data storage 1601 may be included with other on-chip or off-chip data storage, including a processor's L1, L2, or L3 cache or system memory.

In at least one embodiment, any portion of code and/or data storage 1601 may be internal or external to one or more processors or other hardware logic devices or circuits. In at least one embodiment, code and/or code and/or data storage 1601 may be cache memory, dynamic randomly addressable memory (“DRAM”), static randomly addressable memory (“SRAM”), non-volatile memory (e.g., flash memory), or other storage. In at least one embodiment, a choice of whether code and/or code and/or data storage 1601 is internal or external to a processor, for example, or comprising DRAM, SRAM, flash or some other storage type may depend on available storage on-chip versus off-chip, latency requirements of training and/or inferencing functions being performed, batch size of data used in inferencing and/or training of a neural network, or some combination of these factors.

In at least one embodiment, inference and/or training logic 1615 may include, without limitation, a code and/or data storage 1605 to store backward and/or output weight and/or input/output data corresponding to neurons or layers of a neural network trained and/or used for inferencing in aspects of one or more embodiments. In at least one embodiment, code and/or data storage 1605 stores weight parameters and/or input/output data of each layer of a neural network trained or used in conjunction with one or more embodiments during backward propagation of input/output data and/or weight parameters during training and/or inferencing using aspects of one or more embodiments. In at least one embodiment, training logic 1615 may include, or be coupled to code and/or data storage 1605 to store graph code or other software to control timing and/or order, in which weight and/or other parameter information is to be loaded to configure, logic, including integer and/or floating point units (collectively, arithmetic logic units (ALUs)).

In at least one embodiment, code, such as graph code, causes the loading of weight or other parameter information into processor ALUs based on an architecture of a neural network to which such code corresponds. In at least one embodiment, any portion of code and/or data storage 1605 may be included with other on-chip or off-chip data storage, including a processor's L1, L2, or L3 cache or system memory. In at least one embodiment, any portion of code and/or data storage 1605 may be internal or external to one or more processors or other hardware logic devices or circuits. In at least one embodiment, code and/or data storage 1605 may be cache memory, DRAM, SRAM, non-volatile memory (e.g., flash memory), or other storage. In at least one embodiment, a choice of whether code and/or data storage 1605 is internal or external to a processor, for example, or comprising DRAM, SRAM, flash memory or some other storage type may depend on available storage on-chip versus off-chip, latency requirements of training and/or inferencing functions being performed, batch size of data used in inferencing and/or training of a neural network, or some combination of these factors.

In at least one embodiment, code and/or data storage 1601 and code and/or data storage 1605 may be separate storage structures. In at least one embodiment, code and/or data storage 1601 and code and/or data storage 1605 may be a combined storage structure. In at least one embodiment, code and/or data storage 1601 and code and/or data storage 1605 may be partially combined and partially separate. In at least one embodiment, any portion of code and/or data storage 1601 and code and/or data storage 1605 may be included with other on-chip or off-chip data storage, including a processor's L1, L2, or L3 cache or system memory.

In at least one embodiment, inference and/or training logic 1615 may include, without limitation, one or more arithmetic logic unit(s) (“ALU(s)”) 1610, including integer and/or floating point units, to perform logical and/or mathematical operations based, at least in part on, or indicated by, training and/or inference code (e.g., graph code), a result of which may produce activations (e.g., output values from layers or neurons within a neural network) stored in an activation storage 1620 that are functions of input/output and/or weight parameter data stored in code and/or data storage 1601 and/or code and/or data storage 1605. In at least one embodiment, activations stored in activation storage 1620 are generated according to linear algebraic and or matrix-based mathematics performed by ALU(s) 1610 in response to performing instructions or other code, wherein weight values stored in code and/or data storage 1605 and/or data storage 1601 are used as operands along with other values, such as bias values, gradient information, momentum values, or other parameters or hyperparameters, any or all of which may be stored in code and/or data storage 1605 or code and/or data storage 1601 or another storage on or off-chip.

In at least one embodiment, ALU(s) 1610 are included within one or more processors or other hardware logic devices or circuits, whereas in another embodiment, ALU(s) 1610 may be external to a processor or other hardware logic device or circuit that uses them (e.g., a co-processor). In at least one embodiment, ALUs 1610 may be included within a processor's execution units or otherwise within a bank of ALUs accessible by a processor's execution units either within same processor or distributed between different processors of different types (e.g., central processing units, graphics processing units, fixed function units, etc.). In at least one embodiment, code and/or data storage 1601, code and/or data storage 1605, and activation storage 1620 may share a processor or other hardware logic device or circuit, whereas in another embodiment, they may be in different processors or other hardware logic devices or circuits, or some combination of same and different processors or other hardware logic devices or circuits. In at least one embodiment, any portion of activation storage 1620 may be included with other on-chip or off-chip data storage, including a processor's L1, L2, or L3 cache or system memory. Furthermore, inferencing and/or training code may be stored with other code accessible to a processor or other hardware logic or circuit and fetched and/or processed using a processor's fetch, decode, scheduling, execution, retirement and/or other logical circuits.

In at least one embodiment, activation storage 1620 may be cache memory, DRAM, SRAM, non-volatile memory (e.g., flash memory), or other storage. In at least one embodiment, activation storage 1620 may be completely or partially within or external to one or more processors or other logical circuits. In at least one embodiment, a choice of whether activation storage 1620 is internal or external to a processor, for example, or comprising DRAM, SRAM, flash memory or some other storage type may depend on available storage on-chip versus off-chip, latency requirements of training and/or inferencing functions being performed, batch size of data used in inferencing and/or training of a neural network, or some combination of these factors.

In at least one embodiment, inference and/or training logic 1615 illustrated in FIG. 16A may be used in conjunction with an application-specific integrated circuit (“ASIC”), such as a TensorFlow® Processing Unit from Google, an inference processing unit (IPU) from Graphcore™, or a Nervana® (e.g., “Lake Crest”) processor from Intel Corp. In at least one embodiment, inference and/or training logic 1615 illustrated in FIG. 16A may be used in conjunction with central processing unit (“CPU”) hardware, graphics processing unit (“GPU”) hardware or other hardware, such as field programmable gate arrays (“FPGAs”).

FIG. 16B illustrates inference and/or training logic 1615, according to at least one embodiment. In at least one embodiment, inference and/or training logic 1615 may include, without limitation, hardware logic in which computational resources are dedicated or otherwise exclusively used in conjunction with weight values or other information corresponding to one or more layers of neurons within a neural network. In at least one embodiment, inference and/or training logic 1615 illustrated in FIG. 16B may be used in conjunction with an application-specific integrated circuit (ASIC), such as TensorFlow® Processing Unit from Google, an inference processing unit (IPU) from Graphcore™, or a Nervana® (e.g., “Lake Crest”) processor from Intel Corp. In at least one embodiment, inference and/or training logic 1615 illustrated in FIG. 16B may be used in conjunction with central processing unit (CPU) hardware, graphics processing unit (GPU) hardware or other hardware, such as field programmable gate arrays (FPGAs). In at least one embodiment, inference and/or training logic 1615 includes, without limitation, code and/or data storage 1601 and code and/or data storage 1605, which may be used to store code (e.g., graph code), weight values and/or other information, including bias values, gradient information, momentum values, and/or other parameter or hyperparameter information. In at least one embodiment illustrated in FIG. 16B, each of code and/or data storage 1601 and code and/or data storage 1605 is associated with a dedicated computational resource, such as computational hardware 1602 and computational hardware 1606, respectively. In at least one embodiment, each of computational hardware 1602 and computational hardware 1606 comprises one or more ALUs that perform mathematical functions, such as linear algebraic functions, only on information stored in code and/or data storage 1601 and code and/or data storage 1605, respectively, result of which is stored in activation storage 1620.

In at least one embodiment, each of code and/or data storage 1601 and 1605 and corresponding computational hardware 1602 and 1606, respectively, correspond to different layers of a neural network, such that resulting activation from one storage/computational pair 1601/1602 of code and/or data storage 1601 and computational hardware 1602 is provided as an input to a next storage/computational pair 1605/1606 of code and/or data storage 1605 and computational hardware 1606, in order to mirror a conceptual organization of a neural network. In at least one embodiment, each of storage/computational pairs 1601/1602 and 1605/1606 may correspond to more than one neural network layer. In at least one embodiment, additional storage/computation pairs (not shown) subsequent to or in parallel with storage/computation pairs 1601/1602 and 1605/1606 may be included in inference and/or training logic 1615.

Neural Network Training and Deployment

FIG. 17 illustrates training and deployment of a deep neural network, according to at least one embodiment. In at least one embodiment, untrained neural network 1706 is trained using a training dataset 1702. In at least one embodiment, training framework 1704 is a PyTorch framework, whereas in other embodiments, training framework 1704 is a TensorFlow, Boost, Caffe, Microsoft Cognitive Toolkit/CNTK, MXNet, Chainer, Keras, Deeplearning4j, or other training framework. In at least one embodiment, training framework 1704 trains an untrained neural network 1706 and enables it to be trained using processing resources described herein to generate a trained neural network 1708. In at least one embodiment, weights may be chosen randomly or by pre-training using a deep belief network. In at least one embodiment, training may be performed in either a supervised, partially supervised, or unsupervised manner.

In at least one embodiment, untrained neural network 1706 is trained using supervised learning, wherein training dataset 1702 includes an input paired with a desired output for an input, or where training dataset 1702 includes input having a known output and an output of neural network 1706 is manually graded. In at least one embodiment, untrained neural network 1706 is trained in a supervised manner and processes inputs from training dataset 1702 and compares resulting outputs against a set of expected or desired outputs. In at least one embodiment, errors are then propagated back through untrained neural network 1706. In at least one embodiment, training framework 1704 adjusts weights that control untrained neural network 1706. In at least one embodiment, training framework 1704 includes tools to monitor how well untrained neural network 1706 is converging towards a model, such as trained neural network 1708, suitable to generating correct answers, such as in result 1714, based on input data such as a new dataset 1712. In at least one embodiment, training framework 1704 trains untrained neural network 1706 repeatedly while adjust weights to refine an output of untrained neural network 1706 using a loss function and adjustment algorithm, such as stochastic gradient descent. In at least one embodiment, training framework 1704 trains untrained neural network 1706 until untrained neural network 1706 achieves a desired accuracy. In at least one embodiment, trained neural network 1708 can then be deployed to implement any number of machine learning operations.

In at least one embodiment, untrained neural network 1706 is trained using unsupervised learning, wherein untrained neural network 1706 attempts to train itself using unlabeled data. In at least one embodiment, unsupervised learning training dataset 1702 will include input data without any associated output data or “ground truth” data. In at least one embodiment, untrained neural network 1706 can learn groupings within training dataset 1702 and can determine how individual inputs are related to untrained dataset 1702. In at least one embodiment, unsupervised training can be used to generate a self-organizing map in trained neural network 1708 capable of performing operations useful in reducing dimensionality of new dataset 1712. In at least one embodiment, unsupervised training can also be used to perform anomaly detection, which allows identification of data points in new dataset 1712 that deviate from normal patterns of new dataset 1712.

In at least one embodiment, semi-supervised learning may be used, which is a technique in which in training dataset 1702 includes a mix of labeled and unlabeled data. In at least one embodiment, training framework 1704 may be used to perform incremental learning, such as through transferred learning techniques. In at least one embodiment, incremental learning enables trained neural network 1708 to adapt to new dataset 1712 without forgetting knowledge instilled within trained neural network 1708 during initial training.

Data Center

FIG. 18 illustrates an example data center 1800, in which at least one embodiment may be used. In at least one embodiment, data center 1800 includes a data center infrastructure layer 1810, a framework layer 1820, a software layer 1830 and an application layer 1840.

In at least one embodiment, as shown in FIG. 18 , data center infrastructure layer 1810 may include a resource orchestrator 1812, grouped computing resources 1814, and node computing resources (“node C.R.s”) 1816(1)-1816(N), where “N” represents a positive integer (which may be a different integer “N” than used in other figures). In at least one embodiment, node C.R.s 1816(1)-1816(N) may include, but are not limited to, any number of central processing units (“CPUs”) or other processors (including accelerators, field programmable gate arrays (FPGAs), graphics processors, etc.), memory storage devices 1818(1)-1818(N) (e.g., dynamic read-only memory, solid state storage or disk drives), network input/output (“NW I/O”) devices, network switches, virtual machines (“VMs”), power modules, and cooling modules, etc. In at least one embodiment, one or more node C.R.s from among node C.R.s 1816(1)-1816(N) may be a server having one or more of above-mentioned computing resources.

In at least one embodiment, grouped computing resources 1814 may include separate groupings of node C.R.s housed within one or more racks (not shown), or many racks housed in data centers at various geographical locations (also not shown). In at least one embodiment, separate groupings of node C.R.s within grouped computing resources 1814 may include grouped compute, network, memory or storage resources that may be configured or allocated to support one or more workloads. In at least one embodiment, several node C.R.s including CPUs or processors may grouped within one or more racks to provide compute resources to support one or more workloads. In at least one embodiment, one or more racks may also include any number of power modules, cooling modules, and network switches, in any combination.

In at least one embodiment, resource orchestrator 1812 may configure or otherwise control one or more node C.R.s 1816(1)-1816(N) and/or grouped computing resources 1814. In at least one embodiment, resource orchestrator 1812 may include a software design infrastructure (“SDI”) management entity for data center 1800. In at least one embodiment, resource orchestrator 1612 may include hardware, software or some combination thereof.

In at least one embodiment, as shown in FIG. 18 , framework layer 1820 includes a job scheduler 1822, a configuration manager 1824, a resource manager 1826 and a distributed file system 1828. In at least one embodiment, framework layer 1820 may include a framework to support software 1832 of software layer 1830 and/or one or more application(s) 1842 of application layer 1840. In at least one embodiment, software 1832 or application(s) 1842 may respectively include web-based service software or applications, such as those provided by Amazon Web Services, Google Cloud and Microsoft Azure. In at least one embodiment, framework layer 1820 may be, but is not limited to, a type of free and open-source software web application framework such as Apache Spark™ (hereinafter “Spark”) that may utilize distributed file system 1828 for large-scale data processing (e.g., “big data”). In at least one embodiment, job scheduler 1832 may include a Spark driver to facilitate scheduling of workloads supported by various layers of data center 1800. In at least one embodiment, configuration manager 1824 may be capable of configuring different layers such as software layer 1830 and framework layer 1820 including Spark and distributed file system 1828 for supporting large-scale data processing. In at least one embodiment, resource manager 1826 may be capable of managing clustered or grouped computing resources mapped to or allocated for support of distributed file system 1828 and job scheduler 1822. In at least one embodiment, clustered or grouped computing resources may include grouped computing resources 1814 at data center infrastructure layer 1810. In at least one embodiment, resource manager 1826 may coordinate with resource orchestrator 1812 to manage these mapped or allocated computing resources.

In at least one embodiment, software 1832 included in software layer 1830 may include software used by at least portions of node C.R.s 1816(1)-1816(N), grouped computing resources 1814, and/or distributed file system 1828 of framework layer 1820. In at least one embodiment, one or more types of software may include, but are not limited to, Internet web page search software, e-mail virus scan software, database software, and streaming video content software.

In at least one embodiment, application(s) 1842 included in application layer 1840 may include one or more types of applications used by at least portions of node C.R.s 1816(1)-1816(N), grouped computing resources 1814, and/or distributed file system 1828 of framework layer 1820. In at least one embodiment, one or more types of applications may include, but are not limited to, any number of a genomics application, a cognitive compute, application and a machine learning application, including training or inferencing software, machine learning framework software (e.g., PyTorch, TensorFlow, Caffe, etc.) or other machine learning applications used in conjunction with one or more embodiments.

In at least one embodiment, any of configuration manager 1824, resource manager 1826, and resource orchestrator 1812 may implement any number and type of self-modifying actions based on any amount and type of data acquired in any technically feasible fashion. In at least one embodiment, self-modifying actions may relieve a data center operator of data center 1800 from making possibly bad configuration decisions and possibly avoiding underutilized and/or poor performing portions of a data center.

In at least one embodiment, data center 1800 may include tools, services, software or other resources to train one or more machine learning models or predict or infer information using one or more machine learning models according to one or more embodiments described herein. For example, in at least one embodiment, a machine learning model may be trained by calculating weight parameters according to a neural network architecture using software and computing resources described above with respect to data center 1800. In at least one embodiment, trained machine learning models corresponding to one or more neural networks may be used to infer or predict information using resources described above with respect to data center 1800 by using weight parameters calculated through one or more training techniques described herein.

In at least one embodiment, data center may use CPUs, application-specific integrated circuits (ASICs), GPUs, FPGAs, or other hardware to perform training and/or inferencing using above-described resources. Moreover, one or more software and/or hardware resources described above may be configured as a service to allow users to train or performing inferencing of information, such as image recognition, speech recognition, or other artificial intelligence services.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 18 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein. In at least on embodiment, a system that determines a grasp pose can be constructed using a computer system as shown and described above.

Autonomous Vehicle

FIG. 19A illustrates an example of an autonomous vehicle 1900, according to at least one embodiment. In at least one embodiment, autonomous vehicle 1900 (alternatively referred to herein as “vehicle 1900”) may be, without limitation, a passenger vehicle, such as a car, a truck, a bus, and/or another type of vehicle that accommodates one or more passengers. In at least one embodiment, vehicle 1900 may be a semi-tractor-trailer truck used for hauling cargo. In at least one embodiment, vehicle 1900 may be an airplane, robotic vehicle, or other kind of vehicle.

Autonomous vehicles may be described in terms of automation levels, defined by National Highway Traffic Safety Administration (“NHTSA”), a division of US Department of Transportation, and Society of Automotive Engineers (“SAE”) “Taxonomy and Definitions for Terms Related to Driving Automation Systems for On-Road Motor Vehicles” (e.g., Standard No. J3016-201806, published on Jun. 15, 2018, Standard No. J3016-201609, published on Sep. 30, 2016, and previous and future versions of this standard). In one or more embodiments, vehicle 1900 may be capable of functionality in accordance with one or more of Level 1 through Level 5 of autonomous driving levels. For example, in at least one embodiment, vehicle 1900 may be capable of conditional automation (Level 3), high automation (Level 4), and/or full automation (Level 5), depending on embodiment.

In at least one embodiment, vehicle 1900 may include, without limitation, components such as a chassis, a vehicle body, wheels (e.g., 2, 4, 6, 8, 18, etc.), tires, axles, and other components of a vehicle. In at least one embodiment, vehicle 1900 may include, without limitation, a propulsion system 1950, such as an internal combustion engine, hybrid electric power plant, an all-electric engine, and/or another propulsion system type. In at least one embodiment, propulsion system 1950 may be connected to a drive train of vehicle 1900, which may include, without limitation, a transmission, to enable propulsion of vehicle 1900. In at least one embodiment, propulsion system 1950 may be controlled in response to receiving signals from a throttle/accelerator(s) 1952.

In at least one embodiment, a steering system 1954, which may include, without limitation, a steering wheel, is used to steer vehicle 1900 (e.g., along a desired path or route) when propulsion system 1950 is operating (e.g., when vehicle 1900 is in motion). In at least one embodiment, steering system 1954 may receive signals from steering actuator(s) 1956. In at least one embodiment, a steering wheel may be optional for full automation (Level 5) functionality. In at least one embodiment, a brake sensor system 1946 may be used to operate vehicle brakes in response to receiving signals from brake actuator(s) 1948 and/or brake sensors.

In at least one embodiment, controller(s) 1936, which may include, without limitation, one or more system on chips (“SoCs”) (not shown in FIG. 19A) and/or graphics processing unit(s) (“GPU(s)”), provide signals (e.g., representative of commands) to one or more components and/or systems of vehicle 1900. For instance, in at least one embodiment, controller(s) 1936 may send signals to operate vehicle brakes via brake actuator(s) 1948, to operate steering system 1954 via steering actuator(s) 1956, to operate propulsion system 1950 via throttle/accelerator(s) 1952. In at least one embodiment, controller(s) 1936 may include one or more onboard (e.g., integrated) computing devices that process sensor signals, and output operation commands (e.g., signals representing commands) to enable autonomous driving and/or to assist a human driver in driving vehicle 1900. In at least one embodiment, controller(s) 1936 may include a first controller for autonomous driving functions, a second controller for functional safety functions, a third controller for artificial intelligence functionality (e.g., computer vision), a fourth controller for infotainment functionality, a fifth controller for redundancy in emergency conditions, and/or other controllers. In at least one embodiment, a single controller may handle two or more of above functionalities, two or more controllers may handle a single functionality, and/or any combination thereof.

In at least one embodiment, controller(s) 1936 provide signals for controlling one or more components and/or systems of vehicle 1900 in response to sensor data received from one or more sensors (e.g., sensor inputs). In at least one embodiment, sensor data may be received from, for example and without limitation, global navigation satellite systems (“GNSS”) sensor(s) 1958 (e.g., Global Positioning System sensor(s)), RADAR sensor(s) 1960, ultrasonic sensor(s) 1962, LIDAR sensor(s) 1964, inertial measurement unit (“IMU”) sensor(s) 1966 (e.g., accelerometer(s), gyroscope(s), a magnetic compass or magnetic compasses, magnetometer(s), etc.), microphone(s) 1996, stereo camera(s) 1968, wide-view camera(s) 1970 (e.g., fisheye cameras), infrared camera(s) 1972, surround camera(s) 1974 (e.g., 360 degree cameras), long-range cameras (not shown in FIG. 19A), mid-range camera(s) (not shown in FIG. 19A), speed sensor(s) 1944 (e.g., for measuring speed of vehicle 1900), vibration sensor(s) 1942, steering sensor(s) 1940, brake sensor(s) (e.g., as part of brake sensor system 1946), and/or other sensor types.

In at least one embodiment, one or more of controller(s) 1936 may receive inputs (e.g., represented by input data) from an instrument cluster 1932 of vehicle 1900 and provide outputs (e.g., represented by output data, display data, etc.) via a human-machine interface (“HMI”) display 1934, an audible annunciator, a loudspeaker, and/or via other components of vehicle 1900. In at least one embodiment, outputs may include information such as vehicle velocity, speed, time, map data (e.g., a High Definition map (not shown in FIG. 19A), location data (e.g., vehicle's 1900 location, such as on a map), direction, location of other vehicles (e.g., an occupancy grid), information about objects and status of objects as perceived by controller(s) 1936, etc. For example, in at least one embodiment, HMI display 1934 may display information about presence of one or more objects (e.g., a street sign, caution sign, traffic light changing, etc.), and/or information about driving maneuvers vehicle has made, is making, or will make (e.g., changing lanes now, taking exit 34B in two miles, etc.).

In at least one embodiment, vehicle 1900 further includes a network interface 1924 which may use wireless antenna(s) 1926 and/or modem(s) to communicate over one or more networks. For example, in at least one embodiment, network interface 1924 may be capable of communication over Long-Term Evolution (“LTE”), Wideband Code Division Multiple Access (“WCDMA”), Universal Mobile Telecommunications System (“UMTS”), Global System for Mobile communication (“GSM”), IMT-CDMA Multi-Carrier (“CDMA2000”) networks, etc. In at least one embodiment, wireless antenna(s) 1926 may also enable communication between objects in environment (e.g., vehicles, mobile devices, etc.), using local area network(s), such as Bluetooth, Bluetooth Low Energy (“LE”), Z-Wave, ZigBee, etc., and/or low power wide-area network(s) (“LPWANs”), such as LoRaWAN, SigFox, etc. Protocols.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 19A for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein. In at least on embodiment, a system that determines a grasp pose for a robotic gripper can be applied to an autonomous vehicle as shown and illustrated above. For example, for an electric car, a robotic arm may be used to connect the car for charging using the techniques described herein. Success of a grasp can be determined as a successful charging connection.

FIG. 19B illustrates an example of camera locations and fields of view for autonomous vehicle 1900 of FIG. 19A, according to at least one embodiment. In at least one embodiment, cameras and respective fields of view are one example embodiment and are not intended to be limiting. For instance, in at least one embodiment, additional and/or alternative cameras may be included and/or cameras may be located at different locations on vehicle 1900.

In at least one embodiment, camera types for cameras may include, but are not limited to, digital cameras that may be adapted for use with components and/or systems of vehicle 1900. In at least one embodiment, camera(s) may operate at automotive safety integrity level (“ASIL”) B and/or at another ASIL. In at least one embodiment, camera types may be capable of any image capture rate, such as 60 frames per second (fps), 1220 fps, 240 fps, etc., depending on embodiment. In at least one embodiment, cameras may be capable of using rolling shutters, global shutters, another type of shutter, or a combination thereof. In at least one embodiment, color filter array may include a red clear clear clear (“RCCC”) color filter array, a red clear clear blue (“RCCB”) color filter array, a red blue green clear (“RBGC”) color filter array, a Foveon X3 color filter array, a Bayer sensors (“RGGB”) color filter array, a monochrome sensor color filter array, and/or another type of color filter array. In at least one embodiment, clear pixel cameras, such as cameras with an RCCC, an RCCB, and/or an RBGC color filter array, may be used in an effort to increase light sensitivity.

In at least one embodiment, one or more of camera(s) may be used to perform advanced driver assistance systems (“ADAS”) functions (e.g., as part of a redundant or fail-safe design). For example, in at least one embodiment, a Multi-Function Mono Camera may be installed to provide functions including lane departure warning, traffic sign assist and intelligent headlamp control. In at least one embodiment, one or more of camera(s) (e.g., all cameras) may record and provide image data (e.g., video) simultaneously.

In at least one embodiment, one or more camera may be mounted in a mounting assembly, such as a custom designed (three-dimensional (“3D”) printed) assembly, in order to cut out stray light and reflections from within vehicle 1900 (e.g., reflections from dashboard reflected in windshield mirrors) which may interfere with camera image data capture abilities. With reference to wing-mirror mounting assemblies, in at least one embodiment, wing-mirror assemblies may be custom 3D printed so that a camera mounting plate matches a shape of a wing-mirror. In at least one embodiment, camera(s) may be integrated into wing-mirrors. In at least one embodiment, for side-view cameras, camera(s) may also be integrated within four pillars at each corner of a cabin.

In at least one embodiment, cameras with a field of view that include portions of an environment in front of vehicle 1900 (e.g., front-facing cameras) may be used for surround view, to help identify forward facing paths and obstacles, as well as aid in, with help of one or more of controller(s) 1936 and/or control SoCs, providing information critical to generating an occupancy grid and/or determining preferred vehicle paths. In at least one embodiment, front-facing cameras may be used to perform many similar ADAS functions as LIDAR, including, without limitation, emergency braking, pedestrian detection, and collision avoidance. In at least one embodiment, front-facing cameras may also be used for ADAS functions and systems including, without limitation, Lane Departure Warnings (“LDW”), Autonomous Cruise Control (“ACC”), and/or other functions such as traffic sign recognition.

In at least one embodiment, a variety of cameras may be used in a front-facing configuration, including, for example, a monocular camera platform that includes a CMOS (“complementary metal oxide semiconductor”) color imager. In at least one embodiment, a wide-view camera 1970 may be used to perceive objects coming into view from a periphery (e.g., pedestrians, crossing traffic or bicycles). Although only one wide-view camera 1970 is illustrated in FIG. 19B, in other embodiments, there may be any number (including zero) wide-view cameras on vehicle 1900. In at least one embodiment, any number of long-range camera(s) 1998 (e.g., a long-view stereo camera pair) may be used for depth-based object detection, especially for objects for which a neural network has not yet been trained. In at least one embodiment, long-range camera(s) 1998 may also be used for object detection and classification, as well as basic object tracking.

In at least one embodiment, any number of stereo camera(s) 1968 may also be included in a front-facing configuration. In at least one embodiment, one or more of stereo camera(s) 1968 may include an integrated control unit comprising a scalable processing unit, which may provide a programmable logic (“FPGA”) and a multi-core micro-processor with an integrated Controller Area Network (“CAN”) or Ethernet interface on a single chip. In at least one embodiment, such a unit may be used to generate a 3D map of an environment of vehicle 1900, including a distance estimate for all points in an image. In at least one embodiment, one or more of stereo camera(s) 1968 may include, without limitation, compact stereo vision sensor(s) that may include, without limitation, two camera lenses (one each on left and right) and an image processing chip that may measure distance from vehicle 1900 to target object and use generated information (e.g., metadata) to activate autonomous emergency braking and lane departure warning functions. In at least one embodiment, other types of stereo camera(s) 1968 may be used in addition to, or alternatively from, those described herein.

In at least one embodiment, cameras with a field of view that include portions of environment to sides of vehicle 1900 (e.g., side-view cameras) may be used for surround view, providing information used to create and update an occupancy grid, as well as to generate side impact collision warnings. For example, in at least one embodiment, surround camera(s) 1974 (e.g., four surround cameras as illustrated in FIG. 19B) could be positioned on vehicle 1900. In at least one embodiment, surround camera(s) 1974 may include, without limitation, any number and combination of wide-view cameras, fisheye camera(s), 360 degree camera(s), and/or similar cameras. For instance, in at least one embodiment, four fisheye cameras may be positioned on a front, a rear, and sides of vehicle 1900. In at least one embodiment, vehicle 1900 may use three surround camera(s) 1974 (e.g., left, right, and rear), and may leverage one or more other camera(s) (e.g., a forward-facing camera) as a fourth surround-view camera.

In at least one embodiment, cameras with a field of view that include portions of an environment behind vehicle 1900 (e.g., rear-view cameras) may be used for parking assistance, surround view, rear collision warnings, and creating and updating an occupancy grid. In at least one embodiment, a wide variety of cameras may be used including, but not limited to, cameras that are also suitable as a front-facing camera(s) (e.g., long-range cameras 1998 and/or mid-range camera(s) 1976, stereo camera(s) 1968), infrared camera(s) 1972, etc.), as described herein.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 19B for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

FIG. 19C is a block diagram illustrating an example system architecture for autonomous vehicle 1900 of FIG. 19A, according to at least one embodiment. In at least one embodiment, each of components, features, and systems of vehicle 1900 in FIG. 19C is illustrated as being connected via a bus 1902. In at least one embodiment, bus 1902 may include, without limitation, a CAN data interface (alternatively referred to herein as a “CAN bus”). In at least one embodiment, a CAN may be a network inside vehicle 1900 used to aid in control of various features and functionality of vehicle 1900, such as actuation of brakes, acceleration, braking, steering, windshield wipers, etc. In at least one embodiment, bus 1902 may be configured to have dozens or even hundreds of nodes, each with its own unique identifier (e.g., a CAN ID). In at least one embodiment, bus 1902 may be read to find steering wheel angle, ground speed, engine revolutions per minute (“RPMs”), button positions, and/or other vehicle status indicators. In at least one embodiment, bus 1902 may be a CAN bus that is ASIL B compliant.

In at least one embodiment, in addition to, or alternatively from CAN, FlexRay and/or Ethernet protocols may be used. In at least one embodiment, there may be any number of busses forming bus 1902, which may include, without limitation, zero or more CAN busses, zero or more FlexRay busses, zero or more Ethernet busses, and/or zero or more other types of busses using different protocols. In at least one embodiment, two or more busses may be used to perform different functions, and/or may be used for redundancy. For example, a first bus may be used for collision avoidance functionality and a second bus may be used for actuation control. In at least one embodiment, each bus of bus 1902 may communicate with any of components of vehicle 1900, and two or more busses of bus 1902 may communicate with corresponding components. In at least one embodiment, each of any number of system(s) on chip(s) (“SoC(s)”) 1904 (such as SoC 1904(A) and SoC 1904(B), each of controller(s) 1936, and/or each computer within vehicle may have access to same input data (e.g., inputs from sensors of vehicle 1900), and may be connected to a common bus, such CAN bus.

In at least one embodiment, vehicle 1900 may include one or more controller(s) 1936, such as those described herein with respect to FIG. 19A. In at least one embodiment, controller(s) 1936 may be used for a variety of functions. In at least one embodiment, controller(s) 1936 may be coupled to any of various other components and systems of vehicle 1900, and may be used for control of vehicle 1900, artificial intelligence of vehicle 1900, infotainment for vehicle 1900, and/or other functions.

In at least one embodiment, vehicle 1900 may include any number of SoCs 1904. In at least one embodiment, each of SoCs 1904 may include, without limitation, central processing units (“CPU(s)”) 1906, graphics processing units (“GPU(s)”) 1908, processor(s) 1910, cache(s) 1912, accelerator(s) 1914, data store(s) 1916, and/or other components and features not illustrated. In at least one embodiment, SoC(s) 1904 may be used to control vehicle 1900 in a variety of platforms and systems. For example, in at least one embodiment, SoC(s) 1904 may be combined in a system (e.g., system of vehicle 1900) with a High Definition (“HD”) map 1922 which may obtain map refreshes and/or updates via network interface 1924 from one or more servers (not shown in FIG. 19C).

In at least one embodiment, CPU(s) 1906 may include a CPU cluster or CPU complex (alternatively referred to herein as a “CCPLEX”). In at least one embodiment, CPU(s) 1906 may include multiple cores and/or level two (“L2”) caches. For instance, in at least one embodiment, CPU(s) 1906 may include eight cores in a coherent multi-processor configuration. In at least one embodiment, CPU(s) 1906 may include four dual-core clusters where each cluster has a dedicated L2 cache (e.g., a 2 megabyte (MB) L2 cache). In at least one embodiment, CPU(s) 1906 (e.g., CCPLEX) may be configured to support simultaneous cluster operations enabling any combination of clusters of CPU(s) 1906 to be active at any given time.

In at least one embodiment, one or more of CPU(s) 1906 may implement power management capabilities that include, without limitation, one or more of following features: individual hardware blocks may be clock-gated automatically when idle to save dynamic power; each core clock may be gated when such core is not actively executing instructions due to execution of Wait for Interrupt (“WFI”)/Wait for Event (“WFE”) instructions; each core may be independently power-gated; each core cluster may be independently clock-gated when all cores are clock-gated or power-gated; and/or each core cluster may be independently power-gated when all cores are power-gated. In at least one embodiment, CPU(s) 1906 may further implement an enhanced algorithm for managing power states, where allowed power states and expected wakeup times are specified, and hardware/microcode determines which best power state to enter for core, cluster, and CCPLEX. In at least one embodiment, processing cores may support simplified power state entry sequences in software with work offloaded to microcode.

In at least one embodiment, GPU(s) 1908 may include an integrated GPU (alternatively referred to herein as an “iGPU”). In at least one embodiment, GPU(s) 1908 may be programmable and may be efficient for parallel workloads. In at least one embodiment, GPU(s) 1908 may use an enhanced tensor instruction set. In on embodiment, GPU(s) 1908 may include one or more streaming microprocessors, where each streaming microprocessor may include a level one (“L1”) cache (e.g., an L1 cache with at least 96 KB storage capacity), and two or more streaming microprocessors may share an L2 cache (e.g., an L2 cache with a 512 KB storage capacity). In at least one embodiment, GPU(s) 1908 may include at least eight streaming microprocessors. In at least one embodiment, GPU(s) 1908 may use compute application programming interface(s) (API(s)). In at least one embodiment, GPU(s) 1908 may use one or more parallel computing platforms and/or programming models (e.g., NVIDIA's CUDA model).

In at least one embodiment, one or more of GPU(s) 1908 may be power-optimized for best performance in automotive and embedded use cases. For example, in one embodiment, GPU(s) 1908 could be fabricated on Fin field-effect transistor (“FinFET”) circuitry. In at least one embodiment, each streaming microprocessor may incorporate a number of mixed-precision processing cores partitioned into multiple blocks. For example, and without limitation, 64 PF32 cores and 32 PF64 cores could be partitioned into four processing blocks. In at least one embodiment, each processing block could be allocated 16 FP32 cores, 8 FP64 cores, 16 INT32 cores, two mixed-precision NVIDIA Tensor cores for deep learning matrix arithmetic, a level zero (“L0”) instruction cache, a warp scheduler, a dispatch unit, and/or a 64 KB register file. In at least one embodiment, streaming microprocessors may include independent parallel integer and floating-point data paths to provide for efficient execution of workloads with a mix of computation and addressing calculations. In at least one embodiment, streaming microprocessors may include independent thread scheduling capability to enable finer-grain synchronization and cooperation between parallel threads. In at least one embodiment, streaming microprocessors may include a combined L1 data cache and shared memory unit in order to improve performance while simplifying programming.

In at least one embodiment, one or more of GPU(s) 1908 may include a high bandwidth memory (“HBM”) and/or a 16 GB HBM2 memory subsystem to provide, in some examples, about 900 GB/second peak memory bandwidth. In at least one embodiment, in addition to, or alternatively from, HBM memory, a synchronous graphics random-access memory (“SGRAM”) may be used, such as a graphics double data rate type five synchronous random-access memory (“GDDR5”).

In at least one embodiment, GPU(s) 1908 may include unified memory technology. In at least one embodiment, address translation services (“ATS”) support may be used to allow GPU(s) 1908 to access CPU(s) 1906 page tables directly. In at least one embodiment, embodiment, when a GPU of GPU(s) 1908 memory management unit (“MMU”) experiences a miss, an address translation request may be transmitted to CPU(s) 1906. In response, 2 CPU of CPU(s) 1906 may look in its page tables for a virtual-to-physical mapping for an address and transmit translation back to GPU(s) 1908, in at least one embodiment. In at least one embodiment, unified memory technology may allow a single unified virtual address space for memory of both CPU(s) 1906 and GPU(s) 1908, thereby simplifying GPU(s) 1908 programming and porting of applications to GPU(s) 1908.

In at least one embodiment, GPU(s) 1908 may include any number of access counters that may keep track of frequency of access of GPU(s) 1908 to memory of other processors. In at least one embodiment, access counter(s) may help ensure that memory pages are moved to physical memory of a processor that is accessing pages most frequently, thereby improving efficiency for memory ranges shared between processors.

In at least one embodiment, one or more of SoC(s) 1904 may include any number of cache(s) 1912, including those described herein. For example, in at least one embodiment, cache(s) 1912 could include a level three (“L3”) cache that is available to both CPU(s) 1906 and GPU(s) 1908 (e.g., that is connected to CPU(s) 1906 and GPU(s) 1908). In at least one embodiment, cache(s) 1912 may include a write-back cache that may keep track of states of lines, such as by using a cache coherence protocol (e.g., MEI, MESI, MSI, etc.). In at least one embodiment, a L3 cache may include 4 MB of memory or more, depending on embodiment, although smaller cache sizes may be used.

In at least one embodiment, one or more of SoC(s) 1904 may include one or more accelerator(s) 1914 (e.g., hardware accelerators, software accelerators, or a combination thereof). In at least one embodiment, SoC(s) 1904 may include a hardware acceleration cluster that may include optimized hardware accelerators and/or large on-chip memory. In at least one embodiment, large on-chip memory (e.g., 4 MB of SRAM), may enable a hardware acceleration cluster to accelerate neural networks and other calculations. In at least one embodiment, a hardware acceleration cluster may be used to complement GPU(s) 1908 and to off-load some of tasks of GPU(s) 1908 (e.g., to free up more cycles of GPU(s) 1908 for performing other tasks). In at least one embodiment, accelerator(s) 1914 could be used for targeted workloads (e.g., perception, convolutional neural networks (“CNNs”), recurrent neural networks (“RNNs”), etc.) that are stable enough to be amenable to acceleration. In at least one embodiment, a CNN may include a region-based or regional convolutional neural networks (“RCNNs”) and Fast RCNNs (e.g., as used for object detection) or other type of CNN.

In at least one embodiment, accelerator(s) 1914 (e.g., hardware acceleration cluster) may include one or more deep learning accelerator (“DLA”). In at least one embodiment, DLA(s) may include, without limitation, one or more Tensor processing units (“TPUs”) that may be configured to provide an additional ten trillion operations per second for deep learning applications and inferencing. In at least one embodiment, TPUs may be accelerators configured to, and optimized for, performing image processing functions (e.g., for CNNs, RCNNs, etc.). In at least one embodiment, DLA(s) may further be optimized for a specific set of neural network types and floating point operations, as well as inferencing. In at least one embodiment, design of DLA(s) may provide more performance per millimeter than a typical general-purpose GPU, and typically vastly exceeds performance of a CPU. In at least one embodiment, TPU(s) may perform several functions, including a single-instance convolution function, supporting, for example, INT8, INT16, and FP16 data types for both features and weights, as well as post-processor functions. In at least one embodiment, DLA(s) may quickly and efficiently execute neural networks, especially CNNs, on processed or unprocessed data for any of a variety of functions, including, for example and without limitation: a CNN for object identification and detection using data from camera sensors; a CNN for distance estimation using data from camera sensors; a CNN for emergency vehicle detection and identification and detection using data from microphones; a CNN for facial recognition and vehicle owner identification using data from camera sensors; and/or a CNN for security and/or safety related events.

In at least one embodiment, DLA(s) may perform any function of GPU(s) 1908, and by using an inference accelerator, for example, a designer may target either DLA(s) or GPU(s) 1908 for any function. For example, in at least one embodiment, a designer may focus processing of CNNs and floating point operations on DLA(s) and leave other functions to GPU(s) 1908 and/or accelerator(s) 1914.

In at least one embodiment, accelerator(s) 1914 may include programmable vision accelerator (“PVA”), which may alternatively be referred to herein as a computer vision accelerator. In at least one embodiment, PVA may be designed and configured to accelerate computer vision algorithms for advanced driver assistance system (“ADAS”) 1938, autonomous driving, augmented reality (“AR”) applications, and/or virtual reality (“VR”) applications. In at least one embodiment, PVA may provide a balance between performance and flexibility. For example, in at least one embodiment, each PVA may include, for example and without limitation, any number of reduced instruction set computer (“RISC”) cores, direct memory access (“DMA”), and/or any number of vector processors.

In at least one embodiment, RISC cores may interact with image sensors (e.g., image sensors of any cameras described herein), image signal processor(s), etc. In at least one embodiment, each RISC core may include any amount of memory. In at least one embodiment, RISC cores may use any of a number of protocols, depending on embodiment. In at least one embodiment, RISC cores may execute a real-time operating system (“RTOS”). In at least one embodiment, RISC cores may be implemented using one or more integrated circuit devices, application specific integrated circuits (“ASICs”), and/or memory devices. For example, in at least one embodiment, RISC cores could include an instruction cache and/or a tightly coupled RAM.

In at least one embodiment, DMA may enable components of PVA to access system memory independently of CPU(s) 1906. In at least one embodiment, DMA may support any number of features used to provide optimization to a PVA including, but not limited to, supporting multi-dimensional addressing and/or circular addressing. In at least one embodiment, DMA may support up to six or more dimensions of addressing, which may include, without limitation, block width, block height, block depth, horizontal block stepping, vertical block stepping, and/or depth stepping.

In at least one embodiment, vector processors may be programmable processors that may be designed to efficiently and flexibly execute programming for computer vision algorithms and provide signal processing capabilities. In at least one embodiment, a PVA may include a PVA core and two vector processing subsystem partitions. In at least one embodiment, a PVA core may include a processor subsystem, DMA engine(s) (e.g., two DMA engines), and/or other peripherals. In at least one embodiment, a vector processing subsystem may operate as a primary processing engine of a PVA, and may include a vector processing unit (“VPU”), an instruction cache, and/or vector memory (e.g., “VMEM”). In at least one embodiment, VPU core may include a digital signal processor such as, for example, a single instruction, multiple data (“SIMD”), very long instruction word (“VLIW”) digital signal processor. In at least one embodiment, a combination of SIMD and VLIW may enhance throughput and speed.

In at least one embodiment, each of vector processors may include an instruction cache and may be coupled to dedicated memory. As a result, in at least one embodiment, each of vector processors may be configured to execute independently of other vector processors. In at least one embodiment, vector processors that are included in a particular PVA may be configured to employ data parallelism. For instance, in at least one embodiment, plurality of vector processors included in a single PVA may execute a common computer vision algorithm, but on different regions of an image. In at least one embodiment, vector processors included in a particular PVA may simultaneously execute different computer vision algorithms, on one image, or even execute different algorithms on sequential images or portions of an image. In at least one embodiment, among other things, any number of PVAs may be included in hardware acceleration cluster and any number of vector processors may be included in each PVA. In at least one embodiment, PVA may include additional error correcting code (“ECC”) memory, to enhance overall system safety.

In at least one embodiment, accelerator(s) 1914 may include a computer vision network on-chip and static random-access memory (“SRAM”), for providing a high-bandwidth, low latency SRAM for accelerator(s) 1914. In at least one embodiment, on-chip memory may include at least 4 MB SRAM, comprising, for example and without limitation, eight field-configurable memory blocks, that may be accessible by both a PVA and a DLA. In at least one embodiment, each pair of memory blocks may include an advanced peripheral bus (“APB”) interface, configuration circuitry, a controller, and a multiplexer. In at least one embodiment, any type of memory may be used. In at least one embodiment, a PVA and a DLA may access memory via a backbone that provides a PVA and a DLA with high-speed access to memory. In at least one embodiment, a backbone may include a computer vision network on-chip that interconnects a PVA and a DLA to memory (e.g., using APB).

In at least one embodiment, a computer vision network on-chip may include an interface that determines, before transmission of any control signal/address/data, that both a PVA and a DLA provide ready and valid signals. In at least one embodiment, an interface may provide for separate phases and separate channels for transmitting control signals/addresses/data, as well as burst-type communications for continuous data transfer. In at least one embodiment, an interface may comply with International Organization for Standardization (“ISO”) 26262 or International Electrotechnical Commission (“IEC”) 61508 standards, although other standards and protocols may be used.

In at least one embodiment, one or more of SoC(s) 1904 may include a real-time ray-tracing hardware accelerator. In at least one embodiment, real-time ray-tracing hardware accelerator may be used to quickly and efficiently determine positions and extents of objects (e.g., within a world model), to generate real-time visualization simulations, for RADAR signal interpretation, for sound propagation synthesis and/or analysis, for simulation of SONAR systems, for general wave propagation simulation, for comparison to LIDAR data for purposes of localization and/or other functions, and/or for other uses.

In at least one embodiment, accelerator(s) 1914 can have a wide array of uses for autonomous driving. In at least one embodiment, a PVA may be used for key processing stages in ADAS and autonomous vehicles. In at least one embodiment, a PVA's capabilities are a good match for algorithmic domains needing predictable processing, at low power and low latency. In other words, a PVA performs well on semi-dense or dense regular computation, even on small data sets, which might require predictable run-times with low latency and low power. In at least one embodiment, such as in vehicle 1900, PVAs might be designed to run classic computer vision algorithms, as they can be efficient at object detection and operating on integer math.

For example, according to at least one embodiment of technology, a PVA is used to perform computer stereo vision. In at least one embodiment, a semi-global matching-based algorithm may be used in some examples, although this is not intended to be limiting. In at least one embodiment, applications for Level 3-5 autonomous driving use motion estimation/stereo matching on-the-fly (e.g., structure from motion, pedestrian recognition, lane detection, etc.). In at least one embodiment, a PVA may perform computer stereo vision functions on inputs from two monocular cameras.

In at least one embodiment, a PVA may be used to perform dense optical flow. For example, in at least one embodiment, a PVA could process raw RADAR data (e.g., using a 4D Fast Fourier Transform) to provide processed RADAR data. In at least one embodiment, a PVA is used for time of flight depth processing, by processing raw time of flight data to provide processed time of flight data, for example.

In at least one embodiment, a DLA may be used to run any type of network to enhance control and driving safety, including for example and without limitation, a neural network that outputs a measure of confidence for each object detection. In at least one embodiment, confidence may be represented or interpreted as a probability, or as providing a relative “weight” of each detection compared to other detections. In at least one embodiment, a confidence measure enables a system to make further decisions regarding which detections should be considered as true positive detections rather than false positive detections. In at least one embodiment, a system may set a threshold value for confidence and consider only detections exceeding threshold value as true positive detections. In an embodiment in which an automatic emergency braking (“AEB”) system is used, false positive detections would cause vehicle to automatically perform emergency braking, which is obviously undesirable. In at least one embodiment, highly confident detections may be considered as triggers for AEB. In at least one embodiment, a DLA may run a neural network for regressing confidence value. In at least one embodiment, neural network may take as its input at least some subset of parameters, such as bounding box dimensions, ground plane estimate obtained (e.g., from another subsystem), output from IMU sensor(s) 1966 that correlates with vehicle 1900 orientation, distance, 3D location estimates of object obtained from neural network and/or other sensors (e.g., LIDAR sensor(s) 1964 or RADAR sensor(s) 1960), among others.

In at least one embodiment, one or more of SoC(s) 1904 may include data store(s) 1916 (e.g., memory). In at least one embodiment, data store(s) 1916 may be on-chip memory of SoC(s) 1904, which may store neural networks to be executed on GPU(s) 1908 and/or a DLA. In at least one embodiment, data store(s) 1916 may be large enough in capacity to store multiple instances of neural networks for redundancy and safety. In at least one embodiment, data store(s) 1916 may comprise L2 or L3 cache(s).

In at least one embodiment, one or more of SoC(s) 1904 may include any number of processor(s) 1910 (e.g., embedded processors). In at least one embodiment, processor(s) 1910 may include a boot and power management processor that may be a dedicated processor and subsystem to handle boot power and management functions and related security enforcement. In at least one embodiment, a boot and power management processor may be a part of a boot sequence of SoC(s) 1904 and may provide runtime power management services. In at least one embodiment, a boot power and management processor may provide clock and voltage programming, assistance in system low power state transitions, management of SoC(s) 1904 thermals and temperature sensors, and/or management of SoC(s) 1904 power states. In at least one embodiment, each temperature sensor may be implemented as a ring-oscillator whose output frequency is proportional to temperature, and SoC(s) 1904 may use ring-oscillators to detect temperatures of CPU(s) 1906, GPU(s) 1908, and/or accelerator(s) 1914. In at least one embodiment, if temperatures are determined to exceed a threshold, then a boot and power management processor may enter a temperature fault routine and put SoC(s) 1904 into a lower power state and/or put vehicle 1900 into a chauffeur to safe stop mode (e.g., bring vehicle 1900 to a safe stop).

In at least one embodiment, processor(s) 1910 may further include a set of embedded processors that may serve as an audio processing engine which may be an audio subsystem that enables full hardware support for multi-channel audio over multiple interfaces, and a broad and flexible range of audio I/O interfaces. In at least one embodiment, an audio processing engine is a dedicated processor core with a digital signal processor with dedicated RAM.

In at least one embodiment, processor(s) 1910 may further include an always-on processor engine that may provide necessary hardware features to support low power sensor management and wake use cases. In at least one embodiment, an always-on processor engine may include, without limitation, a processor core, a tightly coupled RAM, supporting peripherals (e.g., timers and interrupt controllers), various I/O controller peripherals, and routing logic.

In at least one embodiment, processor(s) 1910 may further include a safety cluster engine that includes, without limitation, a dedicated processor subsystem to handle safety management for automotive applications. In at least one embodiment, a safety cluster engine may include, without limitation, two or more processor cores, a tightly coupled RAM, support peripherals (e.g., timers, an interrupt controller, etc.), and/or routing logic. In a safety mode, two or more cores may operate, in at least one embodiment, in a lockstep mode and function as a single core with comparison logic to detect any differences between their operations. In at least one embodiment, processor(s) 1910 may further include a real-time camera engine that may include, without limitation, a dedicated processor subsystem for handling real-time camera management. In at least one embodiment, processor(s) 1910 may further include a high-dynamic range signal processor that may include, without limitation, an image signal processor that is a hardware engine that is part of a camera processing pipeline.

In at least one embodiment, processor(s) 1910 may include a video image compositor that may be a processing block (e.g., implemented on a microprocessor) that implements video post-processing functions needed by a video playback application to produce a final image for a player window. In at least one embodiment, a video image compositor may perform lens distortion correction on wide-view camera(s) 1970, surround camera(s) 1974, and/or on in-cabin monitoring camera sensor(s). In at least one embodiment, in-cabin monitoring camera sensor(s) are preferably monitored by a neural network running on another instance of SoC 1904, configured to identify in cabin events and respond accordingly. In at least one embodiment, an in-cabin system may perform, without limitation, lip reading to activate cellular service and place a phone call, dictate emails, change a vehicle's destination, activate or change a vehicle's infotainment system and settings, or provide voice-activated web surfing. In at least one embodiment, certain functions are available to a driver when a vehicle is operating in an autonomous mode and are disabled otherwise.

In at least one embodiment, a video image compositor may include enhanced temporal noise reduction for both spatial and temporal noise reduction. For example, in at least one embodiment, where motion occurs in a video, noise reduction weights spatial information appropriately, decreasing weights of information provided by adjacent frames. In at least one embodiment, where an image or portion of an image does not include motion, temporal noise reduction performed by video image compositor may use information from a previous image to reduce noise in a current image.

In at least one embodiment, a video image compositor may also be configured to perform stereo rectification on input stereo lens frames. In at least one embodiment, a video image compositor may further be used for user interface composition when an operating system desktop is in use, and GPU(s) 1908 are not required to continuously render new surfaces. In at least one embodiment, when GPU(s) 1908 are powered on and active doing 3D rendering, a video image compositor may be used to offload GPU(s) 1908 to improve performance and responsiveness.

In at least one embodiment, one or more SoC of SoC(s) 1904 may further include a mobile industry processor interface (“MIPI”) camera serial interface for receiving video and input from cameras, a high-speed interface, and/or a video input block that may be used for a camera and related pixel input functions. In at least one embodiment, one or more of SoC(s) 1904 may further include an input/output controller(s) that may be controlled by software and may be used for receiving I/O signals that are uncommitted to a specific role.

In at least one embodiment, one or more Soc of SoC(s) 1904 may further include a broad range of peripheral interfaces to enable communication with peripherals, audio encoders/decoders (“codecs”), power management, and/or other devices. In at least one embodiment, SoC(s) 1904 may be used to process data from cameras (e.g., connected over Gigabit Multimedia Serial Link and Ethernet channels), sensors (e.g., LIDAR sensor(s) 1964, RADAR sensor(s) 1960, etc. that may be connected over Ethernet channels), data from bus 1902 (e.g., speed of vehicle 1900, steering wheel position, etc.), data from GNSS sensor(s) 1958 (e.g., connected over a Ethernet bus or a CAN bus), etc. In at least one embodiment, one or more SoC of SoC(s) 1904 may further include dedicated high-performance mass storage controllers that may include their own DMA engines, and that may be used to free CPU(s) 1906 from routine data management tasks.

In at least one embodiment, SoC(s) 1904 may be an end-to-end platform with a flexible architecture that spans automation Levels 3-5, thereby providing a comprehensive functional safety architecture that leverages and makes efficient use of computer vision and ADAS techniques for diversity and redundancy, and provides a platform for a flexible, reliable driving software stack, along with deep learning tools. In at least one embodiment, SoC(s) 1904 may be faster, more reliable, and even more energy-efficient and space-efficient than conventional systems. For example, in at least one embodiment, accelerator(s) 1914, when combined with CPU(s) 1906, GPU(s) 1908, and data store(s) 1916, may provide for a fast, efficient platform for Level 3-5 autonomous vehicles.

In at least one embodiment, computer vision algorithms may be executed on CPUs, which may be configured using a high-level programming language, such as C, to execute a wide variety of processing algorithms across a wide variety of visual data. However, in at least one embodiment, CPUs are oftentimes unable to meet performance requirements of many computer vision applications, such as those related to execution time and power consumption, for example. In at least one embodiment, many CPUs are unable to execute complex object detection algorithms in real-time, which is used in in-vehicle ADAS applications and in practical Level 3-5 autonomous vehicles.

Embodiments described herein allow for multiple neural networks to be performed simultaneously and/or sequentially, and for results to be combined together to enable Level 3-5 autonomous driving functionality. For example, in at least one embodiment, a CNN executing on a DLA or a discrete GPU (e.g., GPU(s) 1920) may include text and word recognition, allowing reading and understanding of traffic signs, including signs for which a neural network has not been specifically trained. In at least one embodiment, a DLA may further include a neural network that is able to identify, interpret, and provide semantic understanding of a sign, and to pass that semantic understanding to path planning modules running on a CPU Complex.

In at least one embodiment, multiple neural networks may be run simultaneously, as for Level 3, 4, or 5 driving. For example, in at least one embodiment, a warning sign stating “Caution: flashing lights indicate icy conditions,” along with an electric light, may be independently or collectively interpreted by several neural networks. In at least one embodiment, such warning sign itself may be identified as a traffic sign by a first deployed neural network (e.g., a neural network that has been trained), text “flashing lights indicate icy conditions” may be interpreted by a second deployed neural network, which informs a vehicle's path planning software (preferably executing on a CPU Complex) that when flashing lights are detected, icy conditions exist. In at least one embodiment, a flashing light may be identified by operating a third deployed neural network over multiple frames, informing a vehicle's path-planning software of a presence (or an absence) of flashing lights. In at least one embodiment, all three neural networks may run simultaneously, such as within a DLA and/or on GPU(s) 1908.

In at least one embodiment, a CNN for facial recognition and vehicle owner identification may use data from camera sensors to identify presence of an authorized driver and/or owner of vehicle 1900. In at least one embodiment, an always-on sensor processing engine may be used to unlock a vehicle when an owner approaches a driver door and turns on lights, and, in a security mode, to disable such vehicle when an owner leaves such vehicle. In this way, SoC(s) 1904 provide for security against theft and/or carjacking.

In at least one embodiment, a CNN for emergency vehicle detection and identification may use data from microphones 1996 to detect and identify emergency vehicle sirens. In at least one embodiment, SoC(s) 1904 use a CNN for classifying environmental and urban sounds, as well as classifying visual data. In at least one embodiment, a CNN running on a DLA is trained to identify a relative closing speed of an emergency vehicle (e.g., by using a Doppler effect). In at least one embodiment, a CNN may also be trained to identify emergency vehicles specific to a local area in which a vehicle is operating, as identified by GNSS sensor(s) 1958. In at least one embodiment, when operating in Europe, a CNN will seek to detect European sirens, and when in North America, a CNN will seek to identify only North American sirens. In at least one embodiment, once an emergency vehicle is detected, a control program may be used to execute an emergency vehicle safety routine, slowing a vehicle, pulling over to a side of a road, parking a vehicle, and/or idling a vehicle, with assistance of ultrasonic sensor(s) 1962, until emergency vehicles pass.

In at least one embodiment, vehicle 1900 may include CPU(s) 1918 (e.g., discrete CPU(s), or dCPU(s)), that may be coupled to SoC(s) 1904 via a high-speed interconnect (e.g., PCIe). In at least one embodiment, CPU(s) 1918 may include an X86 processor, for example. CPU(s) 1918 may be used to perform any of a variety of functions, including arbitrating potentially inconsistent results between ADAS sensors and SoC(s) 1904, and/or monitoring status and health of controller(s) 1936 and/or an infotainment system on a chip (“infotainment SoC”) 1930, for example.

In at least one embodiment, vehicle 1900 may include GPU(s) 1920 (e.g., discrete GPU(s), or dGPU(s)), that may be coupled to SoC(s) 1904 via a high-speed interconnect (e.g., NVIDIA's NVLINK channel). In at least one embodiment, GPU(s) 1920 may provide additional artificial intelligence functionality, such as by executing redundant and/or different neural networks, and may be used to train and/or update neural networks based at least in part on input (e.g., sensor data) from sensors of a vehicle 1900.

In at least one embodiment, vehicle 1900 may further include network interface 1924 which may include, without limitation, wireless antenna(s) 1926 (e.g., one or more wireless antennas for different communication protocols, such as a cellular antenna, a Bluetooth antenna, etc.). In at least one embodiment, network interface 1924 may be used to enable wireless connectivity to Internet cloud services (e.g., with server(s) and/or other network devices), with other vehicles, and/or with computing devices (e.g., client devices of passengers). In at least one embodiment, to communicate with other vehicles, a direct link may be established between vehicle 190 and another vehicle and/or an indirect link may be established (e.g., across networks and over the Internet). In at least one embodiment, direct links may be provided using a vehicle-to-vehicle communication link. In at least one embodiment, a vehicle-to-vehicle communication link may provide vehicle 1900 information about vehicles in proximity to vehicle 1900 (e.g., vehicles in front of, on a side of, and/or behind vehicle 1900). In at least one embodiment, such aforementioned functionality may be part of a cooperative adaptive cruise control functionality of vehicle 1900.

In at least one embodiment, network interface 1924 may include an SoC that provides modulation and demodulation functionality and enables controller(s) 1936 to communicate over wireless networks. In at least one embodiment, network interface 1924 may include a radio frequency front-end for up-conversion from baseband to radio frequency, and down conversion from radio frequency to baseband. In at least one embodiment, frequency conversions may be performed in any technically feasible fashion. For example, frequency conversions could be performed through well-known processes, and/or using super-heterodyne processes. In at least one embodiment, radio frequency front end functionality may be provided by a separate chip. In at least one embodiment, network interfaces may include wireless functionality for communicating over LTE, WCDMA, UMTS, GSM, CDMA2000, Bluetooth, Bluetooth LE, Wi-Fi, Z-Wave, ZigBee, LoRaWAN, and/or other wireless protocols.

In at least one embodiment, vehicle 1900 may further include data store(s) 1928 which may include, without limitation, off-chip (e.g., off SoC(s) 1904) storage. In at least one embodiment, data store(s) 1928 may include, without limitation, one or more storage elements including RAM, SRAM, dynamic random-access memory (“DRAM”), video random-access memory (“VRAM”), flash memory, hard disks, and/or other components and/or devices that may store at least one bit of data.

In at least one embodiment, vehicle 1900 may further include GNSS sensor(s) 1958 (e.g., GPS and/or assisted GPS sensors), to assist in mapping, perception, occupancy grid generation, and/or path planning functions. In at least one embodiment, any number of GNSS sensor(s) 1958 may be used, including, for example and without limitation, a GPS using a USB connector with an Ethernet-to-Serial (e.g., RS-232) bridge.

In at least one embodiment, vehicle 1900 may further include RADAR sensor(s) 1960. In at least one embodiment, RADAR sensor(s) 1960 may be used by vehicle 1900 for long-range vehicle detection, even in darkness and/or severe weather conditions. In at least one embodiment, RADAR functional safety levels may be ASIL B. In at least one embodiment, RADAR sensor(s) 1960 may use a CAN bus and/or bus 1902 (e.g., to transmit data generated by RADAR sensor(s) 1960) for control and to access object tracking data, with access to Ethernet channels to access raw data in some examples. In at least one embodiment, a wide variety of RADAR sensor types may be used. For example, and without limitation, RADAR sensor(s) 1960 may be suitable for front, rear, and side RADAR use. In at least one embodiment, one or more sensor of RADAR sensors(s) 1960 is a Pulse Doppler RADAR sensor.

In at least one embodiment, RADAR sensor(s) 1960 may include different configurations, such as long-range with narrow field of view, short-range with wide field of view, short-range side coverage, etc. In at least one embodiment, long-range RADAR may be used for adaptive cruise control functionality. In at least one embodiment, long-range RADAR systems may provide a broad field of view realized by two or more independent scans, such as within a 250 m (meter) range. In at least one embodiment, RADAR sensor(s) 1960 may help in distinguishing between static and moving objects, and may be used by ADAS system 1938 for emergency brake assist and forward collision warning. In at least one embodiment, sensors 1960(s) included in a long-range RADAR system may include, without limitation, monostatic multimodal RADAR with multiple (e.g., six or more) fixed RADAR antennae and a high-speed CAN and FlexRay interface. In at least one embodiment, with six antennae, a central four antennae may create a focused beam pattern, designed to record vehicle's 1900 surroundings at higher speeds with minimal interference from traffic in adjacent lanes. In at least one embodiment, another two antennae may expand field of view, making it possible to quickly detect vehicles entering or leaving a lane of vehicle 1900.

In at least one embodiment, mid-range RADAR systems may include, as an example, a range of up to 160 m (front) or 80 m (rear), and a field of view of up to 42 degrees (front) or 150 degrees (rear). In at least one embodiment, short-range RADAR systems may include, without limitation, any number of RADAR sensor(s) 1960 designed to be installed at both ends of a rear bumper. When installed at both ends of a rear bumper, in at least one embodiment, a RADAR sensor system may create two beams that constantly monitor blind spots in a rear direction and next to a vehicle. In at least one embodiment, short-range RADAR systems may be used in ADAS system 1938 for blind spot detection and/or lane change assist.

In at least one embodiment, vehicle 1900 may further include ultrasonic sensor(s) 1962. In at least one embodiment, ultrasonic sensor(s) 1962, which may be positioned at a front, a back, and/or side location of vehicle 1900, may be used for parking assist and/or to create and update an occupancy grid. In at least one embodiment, a wide variety of ultrasonic sensor(s) 1962 may be used, and different ultrasonic sensor(s) 1962 may be used for different ranges of detection (e.g., 2.5 m, 4 m). In at least one embodiment, ultrasonic sensor(s) 1962 may operate at functional safety levels of ASIL B.

In at least one embodiment, vehicle 1900 may include LIDAR sensor(s) 1964. In at least one embodiment, LIDAR sensor(s) 1964 may be used for object and pedestrian detection, emergency braking, collision avoidance, and/or other functions. In at least one embodiment, LIDAR sensor(s) 1964 may operate at functional safety level ASIL B. In at least one embodiment, vehicle 1900 may include multiple LIDAR sensors 1964 (e.g., two, four, six, etc.) that may use an Ethernet channel (e.g., to provide data to a Gigabit Ethernet switch).

In at least one embodiment, LIDAR sensor(s) 1964 may be capable of providing a list of objects and their distances for a 360-degree field of view. In at least one embodiment, commercially available LIDAR sensor(s) 1964 may have an advertised range of approximately 100 m, with an accuracy of 2 cm to 3 cm, and with support for a 100 Mbps Ethernet connection, for example. In at least one embodiment, one or more non-protruding LIDAR sensors may be used. In such an embodiment, LIDAR sensor(s) 1964 may include a small device that may be embedded into a front, a rear, a side, and/or a corner location of vehicle 1900. In at least one embodiment, LIDAR sensor(s) 1964, in such an embodiment, may provide up to a 120-degree horizontal and 35-degree vertical field-of-view, with a 200 m range even for low-reflectivity objects. In at least one embodiment, front-mounted LIDAR sensor(s) 1964 may be configured for a horizontal field of view between 45 degrees and 135 degrees.

In at least one embodiment, LIDAR technologies, such as 3D flash LIDAR, may also be used. In at least one embodiment, 3D flash LIDAR uses a flash of a laser as a transmission source, to illuminate surroundings of vehicle 1900 up to approximately 200 m. In at least one embodiment, a flash LIDAR unit includes, without limitation, a receptor, which records laser pulse transit time and reflected light on each pixel, which in turn corresponds to a range from vehicle 1900 to objects. In at least one embodiment, flash LIDAR may allow for highly accurate and distortion-free images of surroundings to be generated with every laser flash. In at least one embodiment, four flash LIDAR sensors may be deployed, one at each side of vehicle 1900. In at least one embodiment, 3D flash LIDAR systems include, without limitation, a solid-state 3D staring array LIDAR camera with no moving parts other than a fan (e.g., a non-scanning LIDAR device). In at least one embodiment, flash LIDAR device may use a 5 nanosecond class I (eye-safe) laser pulse per frame and may capture reflected laser light as a 3D range point cloud and co-registered intensity data.

In at least one embodiment, vehicle 1900 may further include IMU sensor(s) 1966. In at least one embodiment, IMU sensor(s) 1966 may be located at a center of a rear axle of vehicle 1900. In at least one embodiment, IMU sensor(s) 1966 may include, for example and without limitation, accelerometer(s), magnetometer(s), gyroscope(s), a magnetic compass, magnetic compasses, and/or other sensor types. In at least one embodiment, such as in six-axis applications, IMU sensor(s) 1966 may include, without limitation, accelerometers and gyroscopes. In at least one embodiment, such as in nine-axis applications, IMU sensor(s) 1966 may include, without limitation, accelerometers, gyroscopes, and magnetometers.

In at least one embodiment, IMU sensor(s) 1966 may be implemented as a miniature, high performance GPS-Aided Inertial Navigation System (“GPS/INS”) that combines micro-electro-mechanical systems (“MEMS”) inertial sensors, a high-sensitivity GPS receiver, and advanced Kalman filtering algorithms to provide estimates of position, velocity, and attitude. In at least one embodiment, IMU sensor(s) 1966 may enable vehicle 1900 to estimate its heading without requiring input from a magnetic sensor by directly observing and correlating changes in velocity from a GPS to IMU sensor(s) 1966. In at least one embodiment, IMU sensor(s) 1966 and GNSS sensor(s) 1958 may be combined in a single integrated unit.

In at least one embodiment, vehicle 1900 may include microphone(s) 1996 placed in and/or around vehicle 1900. In at least one embodiment, microphone(s) 1996 may be used for emergency vehicle detection and identification, among other things.

In at least one embodiment, vehicle 1900 may further include any number of camera types, including stereo camera(s) 1968, wide-view camera(s) 1970, infrared camera(s) 1972, surround camera(s) 1974, long-range camera(s) 1998, mid-range camera(s) 1976, and/or other camera types. In at least one embodiment, cameras may be used to capture image data around an entire periphery of vehicle 1900. In at least one embodiment, which types of cameras used depends on vehicle 1900. In at least one embodiment, any combination of camera types may be used to provide necessary coverage around vehicle 1900. In at least one embodiment, a number of cameras deployed may differ depending on embodiment. For example, in at least one embodiment, vehicle 1900 could include six cameras, seven cameras, ten cameras, twelve cameras, or another number of cameras. In at least one embodiment, cameras may support, as an example and without limitation, Gigabit Multimedia Serial Link (“GMSL”) and/or Gigabit Ethernet communications. In at least one embodiment, each camera might be as described with more detail previously herein with respect to FIG. 19A and FIG. 19B.

In at least one embodiment, vehicle 1900 may further include vibration sensor(s) 1942. In at least one embodiment, vibration sensor(s) 1942 may measure vibrations of components of vehicle 1900, such as axle(s). For example, in at least one embodiment, changes in vibrations may indicate a change in road surfaces. In at least one embodiment, when two or more vibration sensors 1942 are used, differences between vibrations may be used to determine friction or slippage of road surface (e.g., when a difference in vibration is between a power-driven axle and a freely rotating axle).

In at least one embodiment, vehicle 1900 may include ADAS system 1938. In at least one embodiment, ADAS system 1938 may include, without limitation, an SoC, in some examples. In at least one embodiment, ADAS system 1938 may include, without limitation, any number and combination of an autonomous/adaptive/automatic cruise control (“ACC”) system, a cooperative adaptive cruise control (“CACC”) system, a forward crash warning (“FCW”) system, an automatic emergency braking (“AEB”) system, a lane departure warning (“LDW)” system, a lane keep assist (“LKA”) system, a blind spot warning (“BSW”) system, a rear cross-traffic warning (“RCTW”) system, a collision warning (“CW”) system, a lane centering (“LC”) system, and/or other systems, features, and/or functionality.

In at least one embodiment, ACC system may use RADAR sensor(s) 1960, LIDAR sensor(s) 1964, and/or any number of camera(s). In at least one embodiment, ACC system may include a longitudinal ACC system and/or a lateral ACC system. In at least one embodiment, a longitudinal ACC system monitors and controls distance to another vehicle immediately ahead of vehicle 1900 and automatically adjusts speed of vehicle 1900 to maintain a safe distance from vehicles ahead. In at least one embodiment, a lateral ACC system performs distance keeping, and advises vehicle 1900 to change lanes when necessary. In at least one embodiment, a lateral ACC is related to other ADAS applications, such as LC and CW.

In at least one embodiment, a CACC system uses information from other vehicles that may be received via network interface 1924 and/or wireless antenna(s) 1926 from other vehicles via a wireless link, or indirectly, over a network connection (e.g., over the Internet). In at least one embodiment, direct links may be provided by a vehicle-to-vehicle (“V2V”) communication link, while indirect links may be provided by an infrastructure-to-vehicle (“I2V”) communication link. In general, V2V communication provides information about immediately preceding vehicles (e.g., vehicles immediately ahead of and in same lane as vehicle 1900), while I2V communication provides information about traffic further ahead. In at least one embodiment, a CACC system may include either or both I2V and V2V information sources. In at least one embodiment, given information of vehicles ahead of vehicle 1900, a CACC system may be more reliable and it has potential to improve traffic flow smoothness and reduce congestion on road.

In at least one embodiment, an FCW system is designed to alert a driver to a hazard, so that such driver may take corrective action. In at least one embodiment, an FCW system uses a front-facing camera and/or RADAR sensor(s) 1960, coupled to a dedicated processor, DSP, FPGA, and/or ASIC, that is electrically coupled to provide driver feedback, such as a display, speaker, and/or vibrating component. In at least one embodiment, an FCW system may provide a warning, such as in form of a sound, visual warning, vibration and/or a quick brake pulse.

In at least one embodiment, an AEB system detects an impending forward collision with another vehicle or other object, and may automatically apply brakes if a driver does not take corrective action within a specified time or distance parameter. In at least one embodiment, AEB system may use front-facing camera(s) and/or RADAR sensor(s) 1960, coupled to a dedicated processor, DSP, FPGA, and/or ASIC. In at least one embodiment, when an AEB system detects a hazard, it will typically first alert a driver to take corrective action to avoid collision and, if that driver does not take corrective action, that AEB system may automatically apply brakes in an effort to prevent, or at least mitigate, an impact of a predicted collision. In at least one embodiment, an AEB system may include techniques such as dynamic brake support and/or crash imminent braking.

In at least one embodiment, an LDW system provides visual, audible, and/or tactile warnings, such as steering wheel or seat vibrations, to alert driver when vehicle 1900 crosses lane markings. In at least one embodiment, an LDW system does not activate when a driver indicates an intentional lane departure, such as by activating a turn signal. In at least one embodiment, an LDW system may use front-side facing cameras, coupled to a dedicated processor, DSP, FPGA, and/or ASIC, that is electrically coupled to provide driver feedback, such as a display, speaker, and/or vibrating component. In at least one embodiment, an LKA system is a variation of an LDW system. In at least one embodiment, an LKA system provides steering input or braking to correct vehicle 1900 if vehicle 1900 starts to exit its lane.

In at least one embodiment, a BSW system detects and warns a driver of vehicles in an automobile's blind spot. In at least one embodiment, a BSW system may provide a visual, audible, and/or tactile alert to indicate that merging or changing lanes is unsafe. In at least one embodiment, a BSW system may provide an additional warning when a driver uses a turn signal. In at least one embodiment, a BSW system may use rear-side facing camera(s) and/or RADAR sensor(s) 1960, coupled to a dedicated processor, DSP, FPGA, and/or ASIC, that is electrically coupled to driver feedback, such as a display, speaker, and/or vibrating component.

In at least one embodiment, an RCTW system may provide visual, audible, and/or tactile notification when an object is detected outside a rear-camera range when vehicle 1900 is backing up. In at least one embodiment, an RCTW system includes an AEB system to ensure that vehicle brakes are applied to avoid a crash. In at least one embodiment, an RCTW system may use one or more rear-facing RADAR sensor(s) 1960, coupled to a dedicated processor, DSP, FPGA, and/or ASIC, that is electrically coupled to provide driver feedback, such as a display, speaker, and/or vibrating component.

In at least one embodiment, conventional ADAS systems may be prone to false positive results which may be annoying and distracting to a driver, but typically are not catastrophic, because conventional ADAS systems alert a driver and allow that driver to decide whether a safety condition truly exists and act accordingly. In at least one embodiment, vehicle 1900 itself decides, in case of conflicting results, whether to heed result from a primary computer or a secondary computer (e.g., a first controller or a second controller of controllers 1936). For example, in at least one embodiment, ADAS system 1938 may be a backup and/or secondary computer for providing perception information to a backup computer rationality module. In at least one embodiment, a backup computer rationality monitor may run redundant diverse software on hardware components to detect faults in perception and dynamic driving tasks. In at least one embodiment, outputs from ADAS system 1938 may be provided to a supervisory MCU. In at least one embodiment, if outputs from a primary computer and outputs from a secondary computer conflict, a supervisory MCU determines how to reconcile conflict to ensure safe operation.

In at least one embodiment, a primary computer may be configured to provide a supervisory MCU with a confidence score, indicating that primary computer's confidence in a chosen result. In at least one embodiment, if that confidence score exceeds a threshold, that supervisory MCU may follow that primary computer's direction, regardless of whether that secondary computer provides a conflicting or inconsistent result. In at least one embodiment, where a confidence score does not meet a threshold, and where primary and secondary computers indicate different results (e.g., a conflict), a supervisory MCU may arbitrate between computers to determine an appropriate outcome.

In at least one embodiment, a supervisory MCU may be configured to run a neural network(s) that is trained and configured to determine, based at least in part on outputs from a primary computer and outputs from a secondary computer, conditions under which that secondary computer provides false alarms. In at least one embodiment, neural network(s) in a supervisory MCU may learn when a secondary computer's output may be trusted, and when it cannot. For example, in at least one embodiment, when that secondary computer is a RADAR-based FCW system, a neural network(s) in that supervisory MCU may learn when an FCW system is identifying metallic objects that are not, in fact, hazards, such as a drainage grate or manhole cover that triggers an alarm. In at least one embodiment, when a secondary computer is a camera-based LDW system, a neural network in a supervisory MCU may learn to override LDW when bicyclists or pedestrians are present and a lane departure is, in fact, a safest maneuver. In at least one embodiment, a supervisory MCU may include at least one of a DLA or a GPU suitable for running neural network(s) with associated memory. In at least one embodiment, a supervisory MCU may comprise and/or be included as a component of SoC(s) 1904.

In at least one embodiment, ADAS system 1938 may include a secondary computer that performs ADAS functionality using traditional rules of computer vision. In at least one embodiment, that secondary computer may use classic computer vision rules (if-then), and presence of a neural network(s) in a supervisory MCU may improve reliability, safety and performance. For example, in at least one embodiment, diverse implementation and intentional non-identity makes an overall system more fault-tolerant, especially to faults caused by software (or software-hardware interface) functionality. For example, in at least one embodiment, if there is a software bug or error in software running on a primary computer, and non-identical software code running on a secondary computer provides a consistent overall result, then a supervisory MCU may have greater confidence that an overall result is correct, and a bug in software or hardware on that primary computer is not causing a material error.

In at least one embodiment, an output of ADAS system 1938 may be fed into a primary computer's perception block and/or a primary computer's dynamic driving task block. For example, in at least one embodiment, if ADAS system 1938 indicates a forward crash warning due to an object immediately ahead, a perception block may use this information when identifying objects. In at least one embodiment, a secondary computer may have its own neural network that is trained and thus reduces a risk of false positives, as described herein.

In at least one embodiment, vehicle 1900 may further include infotainment SoC 1930 (e.g., an in-vehicle infotainment system (IVI)). Although illustrated and described as an SoC, infotainment system SoC 1930, in at least one embodiment, may not be an SoC, and may include, without limitation, two or more discrete components. In at least one embodiment, infotainment SoC 1930 may include, without limitation, a combination of hardware and software that may be used to provide audio (e.g., music, a personal digital assistant, navigational instructions, news, radio, etc.), video (e.g., TV, movies, streaming, etc.), phone (e.g., hands-free calling), network connectivity (e.g., LTE, WiFi, etc.), and/or information services (e.g., navigation systems, rear-parking assistance, a radio data system, vehicle related information such as fuel level, total distance covered, brake fuel level, oil level, door open/close, air filter information, etc.) to vehicle 1900. For example, infotainment SoC 1930 could include radios, disk players, navigation systems, video players, USB and Bluetooth connectivity, carputers, in-car entertainment, WiFi, steering wheel audio controls, hands free voice control, a heads-up display (“HUD”), HMI display 1934, a telematics device, a control panel (e.g., for controlling and/or interacting with various components, features, and/or systems), and/or other components. In at least one embodiment, infotainment SoC 1930 may further be used to provide information (e.g., visual and/or audible) to user(s) of vehicle 1900, such as information from ADAS system 1938, autonomous driving information such as planned vehicle maneuvers, trajectories, surrounding environment information (e.g., intersection information, vehicle information, road information, etc.), and/or other information.

In at least one embodiment, infotainment SoC 1930 may include any amount and type of GPU functionality. In at least one embodiment, infotainment SoC 1930 may communicate over bus 1902 with other devices, systems, and/or components of vehicle 1900. In at least one embodiment, infotainment SoC 1930 may be coupled to a supervisory MCU such that a GPU of an infotainment system may perform some self-driving functions in event that primary controller(s) 1936 (e.g., primary and/or backup computers of vehicle 1900) fail. In at least one embodiment, infotainment SoC 1930 may put vehicle 1900 into a chauffeur to safe stop mode, as described herein.

In at least one embodiment, vehicle 1900 may further include instrument cluster 1932 (e.g., a digital dash, an electronic instrument cluster, a digital instrument panel, etc.). In at least one embodiment, instrument cluster 1932 may include, without limitation, a controller and/or supercomputer (e.g., a discrete controller or supercomputer). In at least one embodiment, instrument cluster 1932 may include, without limitation, any number and combination of a set of instrumentation such as a speedometer, fuel level, oil pressure, tachometer, odometer, turn indicators, gearshift position indicator, seat belt warning light(s), parking-brake warning light(s), engine-malfunction light(s), supplemental restraint system (e.g., airbag) information, lighting controls, safety system controls, navigation information, etc. In some examples, information may be displayed and/or shared among infotainment SoC 1930 and instrument cluster 1932. In at least one embodiment, instrument cluster 1932 may be included as part of infotainment SoC 1930, or vice versa.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 19C for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

FIG. 19D is a diagram of a system 1976 for communication between cloud-based server(s) and autonomous vehicle 1900 of FIG. 19A, according to at least one embodiment. In at least one embodiment, system 1976 may include, without limitation, server(s) 1978, network(s) 1990, and any number and type of vehicles, including vehicle 1900. In at least one embodiment, server(s) 1978 may include, without limitation, a plurality of GPUs 1984(A)-1984(H) (collectively referred to herein as GPUs 1984), PCIe switches 1982(A)-1982(D) (collectively referred to herein as PCIe switches 1982), and/or CPUs 1980(A)-1980(B) (collectively referred to herein as CPUs 1980). In at least one embodiment, GPUs 1984, CPUs 1980, and PCIe switches 1982 may be interconnected with high-speed interconnects such as, for example and without limitation, NVLink interfaces 1988 developed by NVIDIA and/or PCIe connections 1986. In at least one embodiment, GPUs 1984 are connected via an NVLink and/or NVSwitch SoC and GPUs 1984 and PCIe switches 1982 are connected via PCIe interconnects. Although eight GPUs 1984, two CPUs 1980, and four PCIe switches 1982 are illustrated, this is not intended to be limiting. In at least one embodiment, each of server(s) 1978 may include, without limitation, any number of GPUs 1984, CPUs 1980, and/or PCIe switches 1982, in any combination. For example, in at least one embodiment, server(s) 1978 could each include eight, sixteen, thirty-two, and/or more GPUs 1984.

In at least one embodiment, server(s) 1978 may receive, over network(s) 1990 and from vehicles, image data representative of images showing unexpected or changed road conditions, such as recently commenced road-work. In at least one embodiment, server(s) 1978 may transmit, over network(s) 1990 and to vehicles, neural networks 1992, updated or otherwise, and/or map information 1994, including, without limitation, information regarding traffic and road conditions. In at least one embodiment, updates to map information 1994 may include, without limitation, updates for HD map 1922, such as information regarding construction sites, potholes, detours, flooding, and/or other obstructions. In at least one embodiment, neural networks 1992, and/or map information 1994 may have resulted from new training and/or experiences represented in data received from any number of vehicles in an environment, and/or based at least in part on training performed at a data center (e.g., using server(s) 1978 and/or other servers).

In at least one embodiment, server(s) 1978 may be used to train machine learning models (e.g., neural networks) based at least in part on training data. In at least one embodiment, training data may be generated by vehicles, and/or may be generated in a simulation (e.g., using a game engine). In at least one embodiment, any amount of training data is tagged (e.g., where associated neural network benefits from supervised learning) and/or undergoes other pre-processing. In at least one embodiment, any amount of training data is not tagged and/or pre-processed (e.g., where associated neural network does not require supervised learning). In at least one embodiment, once machine learning models are trained, machine learning models may be used by vehicles (e.g., transmitted to vehicles over network(s) 1990), and/or machine learning models may be used by server(s) 1978 to remotely monitor vehicles.

In at least one embodiment, server(s) 1978 may receive data from vehicles and apply data to up-to-date real-time neural networks for real-time intelligent inferencing. In at least one embodiment, server(s) 1978 may include deep-learning supercomputers and/or dedicated AI computers powered by GPU(s) 1984, such as a DGX and DGX Station machines developed by NVIDIA. However, in at least one embodiment, server(s) 1978 may include deep learning infrastructure that uses CPU-powered data centers.

In at least one embodiment, deep-learning infrastructure of server(s) 1978 may be capable of fast, real-time inferencing, and may use that capability to evaluate and verify health of processors, software, and/or associated hardware in vehicle 1900. For example, in at least one embodiment, deep-learning infrastructure may receive periodic updates from vehicle 1900, such as a sequence of images and/or objects that vehicle 1900 has located in that sequence of images (e.g., via computer vision and/or other machine learning object classification techniques). In at least one embodiment, deep-learning infrastructure may run its own neural network to identify objects and compare them with objects identified by vehicle 1900 and, if results do not match and deep-learning infrastructure concludes that AI in vehicle 1900 is malfunctioning, then server(s) 1978 may transmit a signal to vehicle 1900 instructing a fail-safe computer of vehicle 1900 to assume control, notify passengers, and complete a safe parking maneuver.

In at least one embodiment, server(s) 1978 may include GPU(s) 1984 and one or more programmable inference accelerators (e.g., NVIDIA's TensorRT 3 devices). In at least one embodiment, a combination of GPU-powered servers and inference acceleration may make real-time responsiveness possible. In at least one embodiment, such as where performance is less critical, servers powered by CPUs, FPGAs, and other processors may be used for inferencing. In at least one embodiment, hardware structure(s) 1615 are used to perform one or more embodiments. Details regarding hardware structure(x) 1615 are provided herein in conjunction with FIGS. 16A and/or 16B.

Computer Systems

FIG. 20 is a block diagram illustrating an exemplary computer system, which may be a system with interconnected devices and components, a system-on-a-chip (SOC) or some combination thereof formed with a processor that may include execution units to execute an instruction, according to at least one embodiment. In at least one embodiment, a computer system 2000 may include, without limitation, a component, such as a processor 2002 to employ execution units including logic to perform algorithms for process data, in accordance with present disclosure, such as in embodiment described herein. In at least one embodiment, computer system 2000 may include processors, such as PENTIUM® Processor family, Xeon™ Itanium®, XScale™ and/or StrongARM™, Intel® Core™, or Intel® Nervana™ microprocessors available from Intel Corporation of Santa Clara, Calif., although other systems (including PCs having other microprocessors, engineering workstations, set-top boxes and like) may also be used. In at least one embodiment, computer system 2000 may execute a version of WINDOWS operating system available from Microsoft Corporation of Redmond, Wash., although other operating systems (UNIX and Linux, for example), embedded software, and/or graphical user interfaces, may also be used.

Embodiments may be used in other devices such as handheld devices and embedded applications. Some examples of handheld devices include cellular phones, Internet Protocol devices, digital cameras, personal digital assistants (“PDAs”), and handheld PCs. In at least one embodiment, embedded applications may include a microcontroller, a digital signal processor (“DSP”), system on a chip, network computers (“NetPCs”), set-top boxes, network hubs, wide area network (“WAN”) switches, or any other system that may perform one or more instructions in accordance with at least one embodiment.

In at least one embodiment, computer system 2000 may include, without limitation, processor 2002 that may include, without limitation, one or more execution units 2008 to perform machine learning model training and/or inferencing according to techniques described herein. In at least one embodiment, computer system 2000 is a single processor desktop or server system, but in another embodiment, computer system 2000 may be a multiprocessor system. In at least one embodiment, processor 2002 may include, without limitation, a complex instruction set computer (“CISC”) microprocessor, a reduced instruction set computing (“RISC”) microprocessor, a very long instruction word (“VLIW”) microprocessor, a processor implementing a combination of instruction sets, or any other processor device, such as a digital signal processor, for example. In at least one embodiment, processor 2002 may be coupled to a processor bus 2010 that may transmit data signals between processor 2002 and other components in computer system 2000.

In at least one embodiment, processor 2002 may include, without limitation, a Level 1 (“L1”) internal cache memory (“cache”) 2004. In at least one embodiment, processor 2002 may have a single internal cache or multiple levels of internal cache. In at least one embodiment, cache memory may reside external to processor 2002. Other embodiments may also include a combination of both internal and external caches depending on particular implementation and needs. In at least one embodiment, a register file 2006 may store different types of data in various registers including, without limitation, integer registers, floating point registers, status registers, and an instruction pointer register.

In at least one embodiment, execution unit 2008, including, without limitation, logic to perform integer and floating point operations, also resides in processor 2002. In at least one embodiment, processor 2002 may also include a microcode (“ucode”) read only memory (“ROM”) that stores microcode for certain macro instructions. In at least one embodiment, execution unit 2008 may include logic to handle a packed instruction set 2009. In at least one embodiment, by including packed instruction set 2009 in an instruction set of a general-purpose processor, along with associated circuitry to execute instructions, operations used by many multimedia applications may be performed using packed data in processor 2002. In one or more embodiments, many multimedia applications may be accelerated and executed more efficiently by using a full width of a processor's data bus for performing operations on packed data, which may eliminate a need to transfer smaller units of data across that processor's data bus to perform one or more operations one data element at a time.

In at least one embodiment, execution unit 2008 may also be used in microcontrollers, embedded processors, graphics devices, DSPs, and other types of logic circuits. In at least one embodiment, computer system 2000 may include, without limitation, a memory 2020. In at least one embodiment, memory 2020 may be a Dynamic Random Access Memory (“DRAM”) device, a Static Random Access Memory (“SRAM”) device, a flash memory device, or another memory device. In at least one embodiment, memory 2020 may store instruction(s) 2019 and/or data 2021 represented by data signals that may be executed by processor 2002.

In at least one embodiment, a system logic chip may be coupled to processor bus 2010 and memory 2020. In at least one embodiment, a system logic chip may include, without limitation, a memory controller hub (“MCH”) 2016, and processor 2002 may communicate with MCH 2016 via processor bus 2010. In at least one embodiment, MCH 2016 may provide a high bandwidth memory path 2018 to memory 2020 for instruction and data storage and for storage of graphics commands, data and textures. In at least one embodiment, MCH 2016 may direct data signals between processor 2002, memory 2020, and other components in computer system 2000 and to bridge data signals between processor bus 2010, memory 2020, and a system I/O interface 2022. In at least one embodiment, a system logic chip may provide a graphics port for coupling to a graphics controller. In at least one embodiment, MCH 2016 may be coupled to memory 2020 through high bandwidth memory path 2018 and a graphics/video card 2012 may be coupled to MCH 2016 through an Accelerated Graphics Port (“AGP”) interconnect 2014.

In at least one embodiment, computer system 2000 may use system I/O interface 2022 as a proprietary hub interface bus to couple MCH 2016 to an I/O controller hub (“ICH”) 2030. In at least one embodiment, ICH 2030 may provide direct connections to some I/O devices via a local I/O bus. In at least one embodiment, a local I/O bus may include, without limitation, a high-speed I/O bus for connecting peripherals to memory 2020, a chipset, and processor 2002. Examples may include, without limitation, an audio controller 2029, a firmware hub (“flash BIOS”) 2028, a wireless transceiver 2026, a data storage 2024, a legacy I/O controller 2023 containing user input and keyboard interfaces, a serial expansion port 2027, such as a Universal Serial Bus (“USB”) port, and a network controller 2034. In at least one embodiment, data storage 2024 may comprise a hard disk drive, a floppy disk drive, a CD-ROM device, a flash memory device, or other mass storage device.

In at least one embodiment, FIG. 20 illustrates a system, which includes interconnected hardware devices or “chips”, whereas in other embodiments, FIG. 20 may illustrate an exemplary SoC. In at least one embodiment, devices illustrated in FIG. 20 may be interconnected with proprietary interconnects, standardized interconnects (e.g., PCIe) or some combination thereof. In at least one embodiment, one or more components of computer system 2000 are interconnected using compute express link (CXL) interconnects.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 20 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 21 is a block diagram illustrating an electronic device 2100 for utilizing a processor 2110, according to at least one embodiment. In at least one embodiment, electronic device 2100 may be, for example and without limitation, a notebook, a tower server, a rack server, a blade server, a laptop, a desktop, a tablet, a mobile device, a phone, an embedded computer, or any other suitable electronic device.

In at least one embodiment, electronic device 2100 may include, without limitation, processor 2110 communicatively coupled to any suitable number or kind of components, peripherals, modules, or devices. In at least one embodiment, processor 2110 is coupled using a bus or interface, such as a I²C bus, a System Management Bus (“SMBus”), a Low Pin Count (LPC) bus, a Serial Peripheral Interface (“SPI”), a High Definition Audio (“HDA”) bus, a Serial Advance Technology Attachment (“SATA”) bus, a Universal Serial Bus (“USB”) (versions 1, 2, 3, etc.), or a Universal Asynchronous Receiver/Transmitter (“UART”) bus. In at least one embodiment, FIG. 21 illustrates a system, which includes interconnected hardware devices or “chips”, whereas in other embodiments, FIG. 21 may illustrate an exemplary SoC. In at least one embodiment, devices illustrated in FIG. 21 may be interconnected with proprietary interconnects, standardized interconnects (e.g., PCIe) or some combination thereof. In at least one embodiment, one or more components of FIG. 21 are interconnected using compute express link (CXL) interconnects.

In at least one embodiment, FIG. 21 may include a display 2124, a touch screen 2125, a touch pad 2130, a Near Field Communications unit (“NFC”) 2145, a sensor hub 2140, a thermal sensor 2146, an Express Chipset (“EC”) 2135, a Trusted Platform Module (“TPM”) 2138, BIOS/firmware/flash memory (“BIOS, FW Flash”) 2122, a DSP 2160, a drive 2120 such as a Solid State Disk (“SSD”) or a Hard Disk Drive (“HDD”), a wireless local area network unit (“WLAN”) 2150, a Bluetooth unit 2152, a Wireless Wide Area Network unit (“WWAN”) 2156, a Global Positioning System (GPS) unit 2155, a camera (“USB 3.0 camera”) 2154 such as a USB 3.0 camera, and/or a Low Power Double Data Rate (“LPDDR”) memory unit (“LPDDR3”) 2115 implemented in, for example, an LPDDR3 standard. These components may each be implemented in any suitable manner.

In at least one embodiment, other components may be communicatively coupled to processor 2110 through components described herein. In at least one embodiment, an accelerometer 2141, an ambient light sensor (“ALS”) 2142, a compass 2143, and a gyroscope 2144 may be communicatively coupled to sensor hub 2140. In at least one embodiment, a thermal sensor 2139, a fan 2137, a keyboard 2136, and touch pad 2130 may be communicatively coupled to EC 2135. In at least one embodiment, speakers 2163, headphones 2164, and a microphone (“mic”) 2165 may be communicatively coupled to an audio unit (“audio codec and class D amp”) 2162, which may in turn be communicatively coupled to DSP 2160. In at least one embodiment, audio unit 2162 may include, for example and without limitation, an audio coder/decoder (“codec”) and a class D amplifier. In at least one embodiment, a SIM card (“SIM”) 2157 may be communicatively coupled to WWAN unit 2156. In at least one embodiment, components such as WLAN unit 2150 and Bluetooth unit 2152, as well as WWAN unit 2156 may be implemented in a Next Generation Form Factor (“NGFF”).

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 21 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a computer system as shown and described above. In at least one embodiment, a processor of the computer system executes executable instructions that cause the computer system to determine and refine grasp poses as described herein.

FIG. 22 illustrates a computer system 2200, according to at least one embodiment. In at least one embodiment, computer system 2200 is configured to implement various processes and methods described throughout this disclosure.

In at least one embodiment, computer system 2200 comprises, without limitation, at least one central processing unit (“CPU”) 2202 that is connected to a communication bus 2210 implemented using any suitable protocol, such as PCI (“Peripheral Component Interconnect”), peripheral component interconnect express (“PCI-Express”), AGP (“Accelerated Graphics Port”), HyperTransport, or any other bus or point-to-point communication protocol(s). In at least one embodiment, computer system 2200 includes, without limitation, a main memory 2204 and control logic (e.g., implemented as hardware, software, or a combination thereof) and data are stored in main memory 2204, which may take form of random access memory (“RAM”). In at least one embodiment, a network interface subsystem (“network interface”) 2222 provides an interface to other computing devices and networks for receiving data from and transmitting data to other systems with computer system 2200.

In at least one embodiment, computer system 2200, in at least one embodiment, includes, without limitation, input devices 2208, a parallel processing system 2212, and display devices 2206 that can be implemented using a conventional cathode ray tube (“CRT”), a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, a plasma display, or other suitable display technologies. In at least one embodiment, user input is received from input devices 2208 such as keyboard, mouse, touchpad, microphone, etc. In at least one embodiment, each module described herein can be situated on a single semiconductor platform to form a processing system.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 22 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a computer system as shown and described above. In at least one embodiment, a processor of the computer system executes executable instructions that cause the processor to determine and refine grasp poses as described herein. In at least one embodiment, the executable instructions may be stored on a USB stick as described above.

FIG. 23 illustrates a computer system 2300, according to at least one embodiment. In at least one embodiment, computer system 2300 includes, without limitation, a computer 2310 and a USB stick 2320. In at least one embodiment, computer 2310 may include, without limitation, any number and type of processor(s) (not shown) and a memory (not shown). In at least one embodiment, computer 2310 includes, without limitation, a server, a cloud instance, a laptop, and a desktop computer.

In at least one embodiment, USB stick 2320 includes, without limitation, a processing unit 2330, a USB interface 2340, and USB interface logic 2350. In at least one embodiment, processing unit 2330 may be any instruction execution system, apparatus, or device capable of executing instructions. In at least one embodiment, processing unit 2330 may include, without limitation, any number and type of processing cores (not shown). In at least one embodiment, processing unit 2330 comprises an application specific integrated circuit (“ASIC”) that is optimized to perform any amount and type of operations associated with machine learning. For instance, in at least one embodiment, processing unit 2330 is a tensor processing unit (“TPC”) that is optimized to perform machine learning inference operations. In at least one embodiment, processing unit 2330 is a vision processing unit (“VPU”) that is optimized to perform machine vision and machine learning inference operations.

In at least one embodiment, USB interface 2340 may be any type of USB connector or USB socket. For instance, in at least one embodiment, USB interface 2340 is a USB 3.0 Type-C socket for data and power. In at least one embodiment, USB interface 2340 is a USB 3.0 Type-A connector. In at least one embodiment, USB interface logic 2350 may include any amount and type of logic that enables processing unit 2330 to interface with devices (e.g., computer 2310) via USB connector 2340.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 23 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a computer system as shown and described above. In at least one embodiment, a processor of the computer system executes executable instructions that cause the processor to determine and refine grasp poses as described herein. In at least one embodiment, the executable instructions may be stored on a USB stick as described above.

FIG. 24A illustrates an exemplary architecture in which a plurality of GPUs 2410(1)-2410(N) is communicatively coupled to a plurality of multi-core processors 2405(1)-2405(M) over high-speed links 2440(1)-2440(N) (e.g., buses, point-to-point interconnects, etc.). In at least one embodiment, high-speed links 2440(1)-2440(N) support a communication throughput of 4 GB/s, 30 GB/s, 80 GB/s or higher. In at least one embodiment, various interconnect protocols may be used including, but not limited to, PCIe 4.0 or 5.0 and NVLink 2.0. In various figures, “N” and “M” represent positive integers, values of which may be different from figure to figure.

In addition, and in one embodiment, two or more of GPUs 2410 are interconnected over high-speed links 2429(1)-2429(2), which may be implemented using similar or different protocols/links than those used for high-speed links 2440(1)-2440(N). Similarly, two or more of multi-core processors 2405 may be connected over a high-speed link 2428 which may be symmetric multi-processor (SMP) buses operating at 20 GB/s, 30 GB/s, 120 GB/s or higher. Alternatively, all communication between various system components shown in FIG. 24A may be accomplished using similar protocols/links (e.g., over a common interconnection fabric).

In one embodiment, each multi-core processor 2405 is communicatively coupled to a processor memory 2401(1)-2401(M), via memory interconnects 2426(1)-2426(M), respectively, and each GPU 2410(1)-2410(N) is communicatively coupled to GPU memory 2420(1)-2420(N) over GPU memory interconnects 2450(1)-2450(N), respectively. In at least one embodiment, memory interconnects 2426 and 2450 may utilize similar or different memory access technologies. By way of example, and not limitation, processor memories 2401(1)-2401(M) and GPU memories 2420 may be volatile memories such as dynamic random access memories (DRAMs) (including stacked DRAMs), Graphics DDR SDRAM (GDDR) (e.g., GDDR5, GDDR6), or High Bandwidth Memory (HBM) and/or may be non-volatile memories such as 3D) (Point or Nano-Ram. In at least one embodiment, some portion of processor memories 2401 may be volatile memory and another portion may be non-volatile memory (e.g., using a two-level memory (2LM) hierarchy).

As described herein, although various multi-core processors 2405 and GPUs 2410 may be physically coupled to a particular memory 2401, 2420, respectively, and/or a unified memory architecture may be implemented in which a virtual system address space (also referred to as “effective address” space) is distributed among various physical memories. For example, processor memories 2401(1)-2401(M) may each comprise 64 GB of system memory address space and GPU memories 2420(1)-2420(N) may each comprise 32 GB of system memory address space resulting in a total of 256 GB addressable memory when M=2 and N=4. Other values for N and M are possible.

FIG. 24B illustrates additional details for an interconnection between a multi-core processor 2407 and a graphics acceleration module 2446 in accordance with one exemplary embodiment. In at least one embodiment, graphics acceleration module 2446 may include one or more GPU chips integrated on a line card which is coupled to processor 2407 via high-speed link 2440 (e.g., a PCIe bus, NVLink, etc.). In at least one embodiment, graphics acceleration module 2446 may alternatively be integrated on a package or chip with processor 2407.

In at least one embodiment, processor 2407 includes a plurality of cores 2460A-2460D, each with a translation lookaside buffer (“TLB”) 2461A-2461D and one or more caches 2462A-2462D. In at least one embodiment, cores 2460A-2460D may include various other components for executing instructions and processing data that are not illustrated. In at least one embodiment, caches 2462A-2462D may comprise Level 1 (L1) and Level 2 (L2) caches. In addition, one or more shared caches 2456 may be included in caches 2462A-2462D and shared by sets of cores 2460A-2460D. For example, one embodiment of processor 2407 includes 24 cores, each with its own L1 cache, twelve shared L2 caches, and twelve shared L3 caches. In this embodiment, one or more L2 and L3 caches are shared by two adjacent cores. In at least one embodiment, processor 2407 and graphics acceleration module 2446 connect with system memory 2414, which may include processor memories 2401(1)-2401(M) of FIG. 24A.

In at least one embodiment, coherency is maintained for data and instructions stored in various caches 2462A-2462D, 2456 and system memory 2414 via inter-core communication over a coherence bus 2464. In at least one embodiment, for example, each cache may have cache coherency logic/circuitry associated therewith to communicate to over coherence bus 2464 in response to detected reads or writes to particular cache lines. In at least one embodiment, a cache snooping protocol is implemented over coherence bus 2464 to snoop cache accesses.

In at least one embodiment, a proxy circuit 2425 communicatively couples graphics acceleration module 2446 to coherence bus 2464, allowing graphics acceleration module 2446 to participate in a cache coherence protocol as a peer of cores 2460A-2460D. In particular, in at least one embodiment, an interface 2435 provides connectivity to proxy circuit 2425 over high-speed link 2440 and an interface 2437 connects graphics acceleration module 2446 to high-speed link 2440.

In at least one embodiment, an accelerator integration circuit 2436 provides cache management, memory access, context management, and interrupt management services on behalf of a plurality of graphics processing engines 2431(1)-2431(N) of graphics acceleration module 2446. In at least one embodiment, graphics processing engines 2431(1)-2431(N) may each comprise a separate graphics processing unit (GPU). In at least one embodiment, graphics processing engines 2431(1)-2431(N) alternatively may comprise different types of graphics processing engines within a GPU, such as graphics execution units, media processing engines (e.g., video encoders/decoders), samplers, and blit engines. In at least one embodiment, graphics acceleration module 2446 may be a GPU with a plurality of graphics processing engines 2431(1)-2431(N) or graphics processing engines 2431(1)-2431(N) may be individual GPUs integrated on a common package, line card, or chip.

In at least one embodiment, accelerator integration circuit 2436 includes a memory management unit (MMU) 2439 for performing various memory management functions such as virtual-to-physical memory translations (also referred to as effective-to-real memory translations) and memory access protocols for accessing system memory 2414. In at least one embodiment, MMU 2439 may also include a translation lookaside buffer (TLB) (not shown) for caching virtual/effective to physical/real address translations. In at least one embodiment, a cache 2438 can store commands and data for efficient access by graphics processing engines 2431(1)-2431(N). In at least one embodiment, data stored in cache 2438 and graphics memories 2433(1)-2433(M) is kept coherent with core caches 2462A-2462D, 2456 and system memory 2414, possibly using a fetch unit 2444. As mentioned, this may be accomplished via proxy circuit 2425 on behalf of cache 2438 and memories 2433(1)-2433(M) (e.g., sending updates to cache 2438 related to modifications/accesses of cache lines on processor caches 2462A-2462D, 2456 and receiving updates from cache 2438).

In at least one embodiment, a set of registers 2445 store context data for threads executed by graphics processing engines 2431(1)-2431(N) and a context management circuit 2448 manages thread contexts. For example, context management circuit 2448 may perform save and restore operations to save and restore contexts of various threads during contexts switches (e.g., where a first thread is saved and a second thread is stored so that a second thread can be execute by a graphics processing engine). For example, on a context switch, context management circuit 2448 may store current register values to a designated region in memory (e.g., identified by a context pointer). It may then restore register values when returning to a context. In at least one embodiment, an interrupt management circuit 2447 receives and processes interrupts received from system devices.

In one implementation, virtual/effective addresses from a graphics processing engine 2431 are translated to real/physical addresses in system memory 2414 by MMU 2439. In at least one embodiment, accelerator integration circuit 2436 supports multiple (e.g., 4, 8, 16) graphics accelerator modules 2446 and/or other accelerator devices. In at least one embodiment, graphics accelerator module 2446 may be dedicated to a single application executed on processor 2407 or may be shared between multiple applications. In at least one embodiment, a virtualized graphics execution environment is presented in which resources of graphics processing engines 2431(1)-2431(N) are shared with multiple applications or virtual machines (VMs). In at least one embodiment, resources may be subdivided into “slices” which are allocated to different VMs and/or applications based on processing requirements and priorities associated with VMs and/or applications.

In at least one embodiment, accelerator integration circuit 2436 performs as a bridge to a system for graphics acceleration module 2446 and provides address translation and system memory cache services. In addition, in at least one embodiment, accelerator integration circuit 2436 may provide virtualization facilities for a host processor to manage virtualization of graphics processing engines 2431(1)-2431(N), interrupts, and memory management.

In at least one embodiment, because hardware resources of graphics processing engines 2431(1)-2431(N) are mapped explicitly to a real address space seen by host processor 2407, any host processor can address these resources directly using an effective address value. In at least one embodiment, one function of accelerator integration circuit 2436 is physical separation of graphics processing engines 2431(1)-2431(N) so that they appear to a system as independent units.

In at least one embodiment, one or more graphics memories 2433(1)-2433(M) are coupled to each of graphics processing engines 2431(1)-2431(N), respectively and N=M. In at least one embodiment, graphics memories 2433(1)-2433(M) store instructions and data being processed by each of graphics processing engines 2431(1)-2431(N). In at least one embodiment, graphics memories 2433(1)-2433(M) may be volatile memories such as DRAMs (including stacked DRAMs), GDDR memory (e.g., GDDR5, GDDR6), or HBM, and/or may be non-volatile memories such as 3D XPoint or Nano-Ram.

In one embodiment, to reduce data traffic over high-speed link 2440, biasing techniques are used to ensure that data stored in graphics memories 2433(1)-2433(M) is data which will be used most frequently by graphics processing engines 2431(1)-2431(N) and preferably not used by cores 2460A-2460D (at least not frequently). Similarly, in at least one embodiment, a biasing mechanism attempts to keep data needed by cores (and preferably not graphics processing engines 2431(1)-2431(N)) within caches 2462A-2462D, 2456 and system memory 2414.

FIG. 24C illustrates another exemplary embodiment in which accelerator integration circuit 2436 is integrated within processor 2407. In this embodiment, graphics processing engines 2431(1)-2431(N) communicate directly over high-speed link 2440 to accelerator integration circuit 2436 via interface 2437 and interface 2435 (which, again, may be any form of bus or interface protocol). In at least one embodiment, accelerator integration circuit 2436 may perform similar operations as those described with respect to FIG. 24B, but potentially at a higher throughput given its close proximity to coherence bus 2464 and caches 2462A-2462D, 2456. One embodiment supports different programming models including a dedicated-process programming model (no graphics acceleration module virtualization) and shared programming models (with virtualization), which may include programming models which are controlled by accelerator integration circuit 2436 and programming models which are controlled by graphics acceleration module 2446.

In at least one embodiment, graphics processing engines 2431(1)-2431(N) are dedicated to a single application or process under a single operating system. In at least one embodiment, a single application can funnel other application requests to graphics processing engines 2431(1)-2431(N), providing virtualization within a VM/partition.

In at least one embodiment, graphics processing engines 2431(1)-2431(N), may be shared by multiple VM/application partitions. In at least one embodiment, shared models may use a system hypervisor to virtualize graphics processing engines 2431(1)-2431(N) to allow access by each operating system. In at least one embodiment, for single-partition systems without a hypervisor, graphics processing engines 2431(1)-2431(N) are owned by an operating system. In at least one embodiment, an operating system can virtualize graphics processing engines 2431(1)-2431(N) to provide access to each process or application.

In at least one embodiment, graphics acceleration module 2446 or an individual graphics processing engine 2431(1)-2431(N) selects a process element using a process handle. In at least one embodiment, process elements are stored in system memory 2414 and are addressable using an effective address to real address translation technique described herein. In at least one embodiment, a process handle may be an implementation-specific value provided to a host process when registering its context with graphics processing engine 2431(1)-2431(N) (that is, calling system software to add a process element to a process element linked list). In at least one embodiment, a lower 16-bits of a process handle may be an offset of a process element within a process element linked list.

FIG. 24D illustrates an exemplary accelerator integration slice 2490. In at least one embodiment, a “slice” comprises a specified portion of processing resources of accelerator integration circuit 2436. In at least one embodiment, an application is effective address space 2482 within system memory 2414 stores process elements 2483. In at least one embodiment, process elements 2483 are stored in response to GPU invocations 2481 from applications 2480 executed on processor 2407. In at least one embodiment, a process element 2483 contains process state for corresponding application 2480. In at least one embodiment, a work descriptor (WD) 2484 contained in process element 2483 can be a single job requested by an application or may contain a pointer to a queue of jobs. In at least one embodiment, WD 2484 is a pointer to a job request queue in an application's effective address space 2482.

In at least one embodiment, graphics acceleration module 2446 and/or individual graphics processing engines 2431(1)-2431(N) can be shared by all or a subset of processes in a system. In at least one embodiment, an infrastructure for setting up process states and sending a WD 2484 to a graphics acceleration module 2446 to start a job in a virtualized environment may be included.

In at least one embodiment, a dedicated-process programming model is implementation-specific. In at least one embodiment, in this model, a single process owns graphics acceleration module 2446 or an individual graphics processing engine 2431. In at least one embodiment, when graphics acceleration module 2446 is owned by a single process, a hypervisor initializes accelerator integration circuit 2436 for an owning partition and an operating system initializes accelerator integration circuit 2436 for an owning process when graphics acceleration module 2446 is assigned.

In at least one embodiment, in operation, a WD fetch unit 2491 in accelerator integration slice 2490 fetches next WD 2484, which includes an indication of work to be done by one or more graphics processing engines of graphics acceleration module 2446. In at least one embodiment, data from WD 2484 may be stored in registers 2445 and used by MMU 2439, interrupt management circuit 2447 and/or context management circuit 2448 as illustrated. For example, one embodiment of MMU 2439 includes segment/page walk circuitry for accessing segment/page tables 2486 within an OS virtual address space 2485. In at least one embodiment, interrupt management circuit 2447 may process interrupt events 2492 received from graphics acceleration module 2446. In at least one embodiment, when performing graphics operations, an effective address 2493 generated by a graphics processing engine 2431(1)-2431(N) is translated to a real address by MMU 2439.

In one embodiment, registers 2445 are duplicated for each graphics processing engine 2431(1)-2431(N) and/or graphics acceleration module 2446 and may be initialized by a hypervisor or an operating system. In at least one embodiment, each of these duplicated registers may be included in an accelerator integration slice 2490. Exemplary registers that may be initialized by a hypervisor are shown in Table 1.

TABLE 1 Hypervisor Initialized Registers Register # Description 1 Slice Control Register 2 Real Address (RA) Scheduled Processes Area Pointer 3 Authority Mask Override Register 4 Interrupt Vector Table Entry Offset 5 Interrupt Vector Table Entry Limit 6 State Register 7 Logical Partition ID 8 Real address (RA) Hypervisor Accelerator Utilization Record Pointer 9 Storage Description Register

Exemplary registers that may be initialized by an operating system are shown in Table 2.

TABLE 2 Operating System Initialized Registers Register # Description 1 Process and Thread Identification 2 Effective Address (EA) Context Save/Restore Pointer 3 Virtual Address (VA) Accelerator Utilization Record Pointer 4 Virtual Address (VA) Storage Segment Table Pointer 5 Authority Mask 6 Work descriptor

In at least one embodiment, each WD 2484 is specific to a particular graphics acceleration module 2446 and/or graphics processing engines 2431(1)-2431(N). In at least one embodiment, it contains all information required by a graphics processing engine 2431(1)-2431(N) to do work, or it can be a pointer to a memory location where an application has set up a command queue of work to be completed.

FIG. 24E illustrates additional details for one exemplary embodiment of a shared model. This embodiment includes a hypervisor real address space 2498 in which a process element list 2499 is stored. In at least one embodiment, hypervisor real address space 2498 is accessible via a hypervisor 2496 which virtualizes graphics acceleration module engines for operating system 2495.

In at least one embodiment, shared programming models allow for all or a subset of processes from all or a subset of partitions in a system to use a graphics acceleration module 2446. In at least one embodiment, there are two programming models where graphics acceleration module 2446 is shared by multiple processes and partitions, namely time-sliced shared and graphics directed shared.

In at least one embodiment, in this model, system hypervisor 2496 owns graphics acceleration module 2446 and makes its function available to all operating systems 2495. In at least one embodiment, for a graphics acceleration module 2446 to support virtualization by system hypervisor 2496, graphics acceleration module 2446 may adhere to certain requirements, such as (1) an application's job request must be autonomous (that is, state does not need to be maintained between jobs), or graphics acceleration module 2446 must provide a context save and restore mechanism, (2) an application's job request is guaranteed by graphics acceleration module 2446 to complete in a specified amount of time, including any translation faults, or graphics acceleration module 2446 provides an ability to preempt processing of a job, and (3) graphics acceleration module 2446 must be guaranteed fairness between processes when operating in a directed shared programming model.

In at least one embodiment, application 2480 is required to make an operating system 2495 system call with a graphics acceleration module type, a work descriptor (WD), an authority mask register (AMR) value, and a context save/restore area pointer (CSRP). In at least one embodiment, graphics acceleration module type describes a targeted acceleration function for a system call. In at least one embodiment, graphics acceleration module type may be a system-specific value. In at least one embodiment, WD is formatted specifically for graphics acceleration module 2446 and can be in a form of a graphics acceleration module 2446 command, an effective address pointer to a user-defined structure, an effective address pointer to a queue of commands, or any other data structure to describe work to be done by graphics acceleration module 2446.

In at least one embodiment, an AMR value is an AMR state to use for a current process. In at least one embodiment, a value passed to an operating system is similar to an application setting an AMR. In at least one embodiment, if accelerator integration circuit 2436 (not shown) and graphics acceleration module 2446 implementations do not support a User Authority Mask Override Register (UAMOR), an operating system may apply a current UAMOR value to an AMR value before passing an AMR in a hypervisor call. In at least one embodiment, hypervisor 2496 may optionally apply a current Authority Mask Override Register (AMOR) value before placing an AMR into process element 2483. In at least one embodiment, CSRP is one of registers 2445 containing an effective address of an area in an application's effective address space 2482 for graphics acceleration module 2446 to save and restore context state. In at least one embodiment, this pointer is optional if no state is required to be saved between jobs or when a job is preempted. In at least one embodiment, context save/restore area may be pinned system memory.

Upon receiving a system call, operating system 2495 may verify that application 2480 has registered and been given authority to use graphics acceleration module 2446. In at least one embodiment, operating system 2495 then calls hypervisor 2496 with information shown in Table 3.

TABLE 3 OS to Hypervisor Call Parameters Parameter # Description 1 A work descriptor (WD) 2 An Authority Mask Register (AMR) value (potentially masked) 3 An effective address (EA) Context Save/Restore Area Pointer (CSRP) 4 A process ID (PID) and optional thread ID (TID) 5 A virtual address (VA) accelerator utilization record pointer (AURP) 6 Virtual address of storage segment table pointer (SSTP) 7 A logical interrupt service number (LISN)

In at least one embodiment, upon receiving a hypervisor call, hypervisor 2496 verifies that operating system 2495 has registered and been given authority to use graphics acceleration module 2446. In at least one embodiment, hypervisor 2496 then puts process element 2483 into a process element linked list for a corresponding graphics acceleration module 2446 type. In at least one embodiment, a process element may include information shown in Table 4.

TABLE 4 Process Element Information Element # Description 1 A work descriptor (WD) 2 An Authority Mask Register (AMR) value (potentially masked). 3 An effective address (EA) Context Save/Restore Area Pointer (CSRP) 4 A process ID (PID) and optional thread ID (TID) 5 A virtual address (VA) accelerator utilization record pointer (AURP) 6 Virtual address of storage segment table pointer (SSTP) 7 A logical interrupt service number (LISN) 8 Interrupt vector table, derived from hypervisor call parameters 9 A state register (SR) value 10 A logical partition ID (LPID) 11 A real address (RA) hypervisor accelerator utilization record pointer 12 Storage Descriptor Register (SDR)

In at least one embodiment, hypervisor initializes a plurality of accelerator integration slice 2490 registers 2445.

As illustrated in FIG. 24F, in at least one embodiment, a unified memory is used, addressable via a common virtual memory address space used to access physical processor memories 2401(1)-2401(N) and GPU memories 2420(1)-2420(N). In this implementation, operations executed on GPUs 2410(1)-2410(N) utilize a same virtual/effective memory address space to access processor memories 2401(1)-2401(M) and vice versa, thereby simplifying programmability. In at least one embodiment, a first portion of a virtual/effective address space is allocated to processor memory 2401(1), a second portion to second processor memory 2401(N), a third portion to GPU memory 2420(1), and so on. In at least one embodiment, an entire virtual/effective memory space (sometimes referred to as an effective address space) is thereby distributed across each of processor memories 2401 and GPU memories 2420, allowing any processor or GPU to access any physical memory with a virtual address mapped to that memory.

In one embodiment, bias/coherence management circuitry 2494A-2494E within one or more of MMUs 2439A-2439E ensures cache coherence between caches of one or more host processors (e.g., 2405) and GPUs 2410 and implements biasing techniques indicating physical memories in which certain types of data should be stored. In at least one embodiment, while multiple instances of bias/coherence management circuitry 2494A-2494E are illustrated in FIG. 24F, bias/coherence circuitry may be implemented within an MMU of one or more host processors 2405 and/or within accelerator integration circuit 2436.

One embodiment allows GPU memories 2420 to be mapped as part of system memory, and accessed using shared virtual memory (SVM) technology, but without suffering performance drawbacks associated with full system cache coherence. In at least one embodiment, an ability for GPU memories 2420 to be accessed as system memory without onerous cache coherence overhead provides a beneficial operating environment for GPU offload. In at least one embodiment, this arrangement allows software of host processor 2405 to setup operands and access computation results, without overhead of tradition I/O DMA data copies. In at least one embodiment, such traditional copies involve driver calls, interrupts and memory mapped I/O (MMIO) accesses that are all inefficient relative to simple memory accesses. In at least one embodiment, an ability to access GPU memories 2420 without cache coherence overheads can be critical to execution time of an offloaded computation. In at least one embodiment, in cases with substantial streaming write memory traffic, for example, cache coherence overhead can significantly reduce an effective write bandwidth seen by a GPU 2410. In at least one embodiment, efficiency of operand setup, efficiency of results access, and efficiency of GPU computation may play a role in determining effectiveness of a GPU offload.

In at least one embodiment, selection of GPU bias and host processor bias is driven by a bias tracker data structure. In at least one embodiment, a bias table may be used, for example, which may be a page-granular structure (e.g., controlled at a granularity of a memory page) that includes 1 or 2 bits per GPU-attached memory page. In at least one embodiment, a bias table may be implemented in a stolen memory range of one or more GPU memories 2420, with or without a bias cache in a GPU 2410 (e.g., to cache frequently/recently used entries of a bias table). Alternatively, in at least one embodiment, an entire bias table may be maintained within a GPU.

In at least one embodiment, a bias table entry associated with each access to a GPU attached memory 2420 is accessed prior to actual access to a GPU memory, causing following operations. In at least one embodiment, local requests from a GPU 2410 that find their page in GPU bias are forwarded directly to a corresponding GPU memory 2420. In at least one embodiment, local requests from a GPU that find their page in host bias are forwarded to processor 2405 (e.g., over a high-speed link as described herein). In at least one embodiment, requests from processor 2405 that find a requested page in host processor bias complete a request like a normal memory read. Alternatively, requests directed to a GPU-biased page may be forwarded to a GPU 2410. In at least one embodiment, a GPU may then transition a page to a host processor bias if it is not currently using a page. In at least one embodiment, a bias state of a page can be changed either by a software-based mechanism, a hardware-assisted software-based mechanism, or, for a limited set of cases, a purely hardware-based mechanism.

In at least one embodiment, one mechanism for changing bias state employs an API call (e.g., OpenCL), which, in turn, calls a GPU's device driver which, in turn, sends a message (or enqueues a command descriptor) to a GPU directing it to change a bias state and, for some transitions, perform a cache flushing operation in a host. In at least one embodiment, a cache flushing operation is used for a transition from host processor 2405 bias to GPU bias, but is not for an opposite transition.

In one embodiment, cache coherency is maintained by temporarily rendering GPU-biased pages uncacheable by host processor 2405. In at least one embodiment, to access these pages, processor 2405 may request access from GPU 2410, which may or may not grant access right away. In at least one embodiment, thus, to reduce communication between processor 2405 and GPU 2410 it is beneficial to ensure that GPU-biased pages are those which are required by a GPU but not host processor 2405 and vice versa.

Hardware structure(s) 1615 are used to perform one or more embodiments. Details regarding a hardware structure(s) 1615 may be provided herein in conjunction with FIGS. 16A and/or 16B.

FIG. 25 illustrates exemplary integrated circuits and associated graphics processors that may be fabricated using one or more IP cores, according to various embodiments described herein. In addition to what is illustrated, other logic and circuits may be included in at least one embodiment, including additional graphics processors/cores, peripheral interface controllers, or general-purpose processor cores.

FIG. 25 is a block diagram illustrating an exemplary system on a chip integrated circuit 2500 that may be fabricated using one or more IP cores, according to at least one embodiment. In at least one embodiment, integrated circuit 2500 includes one or more application processor(s) 2505 (e.g., CPUs), at least one graphics processor 2510, and may additionally include an image processor 2515 and/or a video processor 2520, any of which may be a modular IP core. In at least one embodiment, integrated circuit 2500 includes peripheral or bus logic including a USB controller 2525, a UART controller 2530, an SPI/SDIO controller 2535, and an I²2 S/I²2C controller 2540. In at least one embodiment, integrated circuit 2500 can include a display device 2545 coupled to one or more of a high-definition multimedia interface (HDMI) controller 2550 and a mobile industry processor interface (MIPI) display interface 2555. In at least one embodiment, storage may be provided by a flash memory subsystem 2560 including flash memory and a flash memory controller. In at least one embodiment, a memory interface may be provided via a memory controller 2565 for access to SDRAM or SRAM memory devices. In at least one embodiment, some integrated circuits additionally include an embedded security engine 2570.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in integrated circuit 2500 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein. In at least one embodiment, the processor is a graphics processor, GPU, video processor, or application processor as described herein.

FIGS. 26A-26B illustrate exemplary integrated circuits and associated graphics processors that may be fabricated using one or more IP cores, according to various embodiments described herein. In addition to what is illustrated, other logic and circuits may be included in at least one embodiment, including additional graphics processors/cores, peripheral interface controllers, or general-purpose processor cores.

FIGS. 26A-26B are block diagrams illustrating exemplary graphics processors for use within an SoC, according to embodiments described herein. FIG. 26A illustrates an exemplary graphics processor 2610 of a system on a chip integrated circuit that may be fabricated using one or more IP cores, according to at least one embodiment. FIG. 26B illustrates an additional exemplary graphics processor 2640 of a system on a chip integrated circuit that may be fabricated using one or more IP cores, according to at least one embodiment. In at least one embodiment, graphics processor 2610 of FIG. 26A is a low power graphics processor core. In at least one embodiment, graphics processor 2640 of FIG. 26B is a higher performance graphics processor core. In at least one embodiment, each of graphics processors 2610, 2640 can be variants of graphics processor 2510 of FIG. 25 .

In at least one embodiment, graphics processor 2610 includes a vertex processor 2605 and one or more fragment processor(s) 2615A-2615N (e.g., 2615A, 2615B, 2615C, 2615D, through 2615N-1, and 2615N). In at least one embodiment, graphics processor 2610 can execute different shader programs via separate logic, such that vertex processor 2605 is optimized to execute operations for vertex shader programs, while one or more fragment processor(s) 2615A-2615N execute fragment (e.g., pixel) shading operations for fragment or pixel shader programs. In at least one embodiment, vertex processor 2605 performs a vertex processing stage of a 3D graphics pipeline and generates primitives and vertex data. In at least one embodiment, fragment processor(s) 2615A-2615N use primitive and vertex data generated by vertex processor 2605 to produce a framebuffer that is displayed on a display device. In at least one embodiment, fragment processor(s) 2615A-2615N are optimized to execute fragment shader programs as provided for in an OpenGL API, which may be used to perform similar operations as a pixel shader program as provided for in a Direct 3D API.

In at least one embodiment, graphics processor 2610 additionally includes one or more memory management units (MMUs) 2620A-2620B, cache(s) 2625A-2625B, and circuit interconnect(s) 2630A-2630B. In at least one embodiment, one or more MMU(s) 2620A-2620B provide for virtual to physical address mapping for graphics processor 2610, including for vertex processor 2605 and/or fragment processor(s) 2615A-2615N, which may reference vertex or image/texture data stored in memory, in addition to vertex or image/texture data stored in one or more cache(s) 2625A-2625B. In at least one embodiment, one or more MMU(s) 2620A-2620B may be synchronized with other MMUs within a system, including one or more MMUs associated with one or more application processor(s) 2505, image processors 2515, and/or video processors 2520 of FIG. 25 , such that each processor 2505-2520 can participate in a shared or unified virtual memory system. In at least one embodiment, one or more circuit interconnect(s) 2630A-2630B enable graphics processor 2610 to interface with other IP cores within SoC, either via an internal bus of SoC or via a direct connection.

In at least one embodiment, graphics processor 2640 includes one or more shader core(s) 2655A-2655N (e.g., 2655A, 2655B, 2655C, 2655D, 2655E, 2655F, through 2655N-1, and 2655N) as shown in FIG. 26B, which provides for a unified shader core architecture in which a single core or type or core can execute all types of programmable shader code, including shader program code to implement vertex shaders, fragment shaders, and/or compute shaders. In at least one embodiment, a number of shader cores can vary. In at least one embodiment, graphics processor 2640 includes an inter-core task manager 2645, which acts as a thread dispatcher to dispatch execution threads to one or more shader cores 2655A-2655N and a tiling unit 2658 to accelerate tiling operations for tile-based rendering, in which rendering operations for a scene are subdivided in image space, for example to exploit local spatial coherence within a scene or to optimize use of internal caches.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in integrated circuit 26A and/or 26B for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein. In at least one embodiment, the processor is a vertex processor as described herein.

FIGS. 27A-27B illustrate additional exemplary graphics processor logic according to embodiments described herein. FIG. 27A illustrates a graphics core 2700 that may be included within graphics processor 2510 of FIG. 25 , in at least one embodiment, and may be a unified shader core 2655A-2655N as in FIG. 26B in at least one embodiment. FIG. 27B illustrates a highly-parallel general-purpose graphics processing unit (“GPGPU”) 2730 suitable for deployment on a multi-chip module in at least one embodiment.

In at least one embodiment, graphics core 2700 includes a shared instruction cache 2702, a texture unit 2718, and a cache/shared memory 2720 that are common to execution resources within graphics core 2700. In at least one embodiment, graphics core 2700 can include multiple slices 2701A-2701N or a partition for each core, and a graphics processor can include multiple instances of graphics core 2700. In at least one embodiment, slices 2701A-2701N can include support logic including a local instruction cache 2704A-2704N, a thread scheduler 2706A-2706N, a thread dispatcher 2708A-2708N, and a set of registers 2710A-2710N. In at least one embodiment, slices 2701A-2701N can include a set of additional function units (AFUs 2712A-2712N), floating-point units (FPUs 2714A-2714N), integer arithmetic logic units (ALUs 2716A-2716N), address computational units (ACUs 2713A-2713N), double-precision floating-point units (DPFPUs 2715A-2715N), and matrix processing units (MPUs 2717A-2717N).

In at least one embodiment, FPUs 2714A-2714N can perform single-precision (32-bit) and half-precision (16-bit) floating point operations, while DPFPUs 2715A-2715N perform double precision (64-bit) floating point operations. In at least one embodiment, ALUs 2716A-2716N can perform variable precision integer operations at 8-bit, 16-bit, and 32-bit precision, and can be configured for mixed precision operations. In at least one embodiment, MPUs 2717A-2717N can also be configured for mixed precision matrix operations, including half-precision floating point and 8-bit integer operations. In at least one embodiment, MPUs 2717-2717N can perform a variety of matrix operations to accelerate machine learning application frameworks, including enabling support for accelerated general matrix to matrix multiplication (GEMM). In at least one embodiment, AFUs 2712A-2712N can perform additional logic operations not supported by floating-point or integer units, including trigonometric operations (e.g., sine, cosine, etc.).

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in graphics core 2700 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein. In at least one embodiment, the processor is a graphics core as described herein.

FIG. 27B illustrates a general-purpose processing unit (GPGPU) 2730 that can be configured to enable highly-parallel compute operations to be performed by an array of graphics processing units, in at least one embodiment. In at least one embodiment, GPGPU 2730 can be linked directly to other instances of GPGPU 2730 to create a multi-GPU cluster to improve training speed for deep neural networks. In at least one embodiment, GPGPU 2730 includes a host interface 2732 to enable a connection with a host processor. In at least one embodiment, host interface 2732 is a PCI Express interface. In at least one embodiment, host interface 2732 can be a vendor-specific communications interface or communications fabric. In at least one embodiment, GPGPU 2730 receives commands from a host processor and uses a global scheduler 2734 to distribute execution threads associated with those commands to a set of compute clusters 2736A-2736H. In at least one embodiment, compute clusters 2736A-2736H share a cache memory 2738. In at least one embodiment, cache memory 2738 can serve as a higher-level cache for cache memories within compute clusters 2736A-2736H.

In at least one embodiment, GPGPU 2730 includes memory 2744A-2744B coupled with compute clusters 2736A-2736H via a set of memory controllers 2742A-2742B. In at least one embodiment, memory 2744A-2744B can include various types of memory devices including dynamic random access memory (DRAM) or graphics random access memory, such as synchronous graphics random access memory (SGRAM), including graphics double data rate (GDDR) memory.

In at least one embodiment, compute clusters 2736A-2736H each include a set of graphics cores, such as graphics core 2700 of FIG. 27A, which can include multiple types of integer and floating point logic units that can perform computational operations at a range of precisions including suited for machine learning computations. For example, in at least one embodiment, at least a subset of floating point units in each of compute clusters 2736A-2736H can be configured to perform 16-bit or 32-bit floating point operations, while a different subset of floating point units can be configured to perform 64-bit floating point operations.

In at least one embodiment, multiple instances of GPGPU 2730 can be configured to operate as a compute cluster. In at least one embodiment, communication used by compute clusters 2736A-2736H for synchronization and data exchange varies across embodiments. In at least one embodiment, multiple instances of GPGPU 2730 communicate over host interface 2732. In at least one embodiment, GPGPU 2730 includes an I/O hub 2739 that couples GPGPU 2730 with a GPU link 2740 that enables a direct connection to other instances of GPGPU 2730. In at least one embodiment, GPU link 2740 is coupled to a dedicated GPU-to-GPU bridge that enables communication and synchronization between multiple instances of GPGPU 2730. In at least one embodiment, GPU link 2740 couples with a high-speed interconnect to transmit and receive data to other GPGPUs or parallel processors. In at least one embodiment, multiple instances of GPGPU 2730 are located in separate data processing systems and communicate via a network device that is accessible via host interface 2732. In at least one embodiment GPU link 2740 can be configured to enable a connection to a host processor in addition to or as an alternative to host interface 2732.

In at least one embodiment, GPGPU 2730 can be configured to train neural networks. In at least one embodiment, GPGPU 2730 can be used within an inferencing platform. In at least one embodiment, in which GPGPU 2730 is used for inferencing, GPGPU 2730 may include fewer compute clusters 2736A-2736H relative to when GPGPU 2730 is used for training a neural network. In at least one embodiment, memory technology associated with memory 2744A-2744B may differ between inferencing and training configurations, with higher bandwidth memory technologies devoted to training configurations. In at least one embodiment, an inferencing configuration of GPGPU 2730 can support inferencing specific instructions. For example, in at least one embodiment, an inferencing configuration can provide support for one or more 8-bit integer dot product instructions, which may be used during inferencing operations for deployed neural networks.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in GPGPU 2730 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein. In at least one embodiment, the processor is a GPGPU as described herein.

FIG. 28 is a block diagram illustrating a computing system 2800 according to at least one embodiment. In at least one embodiment, computing system 2800 includes a processing subsystem 2801 having one or more processor(s) 2802 and a system memory 2804 communicating via an interconnection path that may include a memory hub 2805. In at least one embodiment, memory hub 2805 may be a separate component within a chipset component or may be integrated within one or more processor(s) 2802. In at least one embodiment, memory hub 2805 couples with an I/O subsystem 2811 via a communication link 2806. In at least one embodiment, I/O subsystem 2811 includes an I/O hub 2807 that can enable computing system 2800 to receive input from one or more input device(s) 2808. In at least one embodiment, I/O hub 2807 can enable a display controller, which may be included in one or more processor(s) 2802, to provide outputs to one or more display device(s) 2810A. In at least one embodiment, one or more display device(s) 2810A coupled with I/O hub 2807 can include a local, internal, or embedded display device.

In at least one embodiment, processing subsystem 2801 includes one or more parallel processor(s) 2812 coupled to memory hub 2805 via a bus or other communication link 2813. In at least one embodiment, communication link 2813 may use one of any number of standards based communication link technologies or protocols, such as, but not limited to PCI Express, or may be a vendor-specific communications interface or communications fabric. In at least one embodiment, one or more parallel processor(s) 2812 form a computationally focused parallel or vector processing system that can include a large number of processing cores and/or processing clusters, such as a many-integrated core (MIC) processor. In at least one embodiment, some or all of parallel processor(s) 2812 form a graphics processing subsystem that can output pixels to one of one or more display device(s) 2810A coupled via I/O Hub 2807. In at least one embodiment, parallel processor(s) 2812 can also include a display controller and display interface (not shown) to enable a direct connection to one or more display device(s) 2810B.

In at least one embodiment, a system storage unit 2814 can connect to I/O hub 2807 to provide a storage mechanism for computing system 2800. In at least one embodiment, an I/O switch 2816 can be used to provide an interface mechanism to enable connections between I/O hub 2807 and other components, such as a network adapter 2818 and/or a wireless network adapter 2819 that may be integrated into platform, and various other devices that can be added via one or more add-in device(s) 2820. In at least one embodiment, network adapter 2818 can be an Ethernet adapter or another wired network adapter. In at least one embodiment, wireless network adapter 2819 can include one or more of a Wi-Fi, Bluetooth, near field communication (NFC), or other network device that includes one or more wireless radios.

In at least one embodiment, computing system 2800 can include other components not explicitly shown, including USB or other port connections, optical storage drives, video capture devices, and like, may also be connected to I/O hub 2807. In at least one embodiment, communication paths interconnecting various components in FIG. 28 may be implemented using any suitable protocols, such as PCI (Peripheral Component Interconnect) based protocols (e.g., PCI-Express), or other bus or point-to-point communication interfaces and/or protocol(s), such as NV-Link high-speed interconnect, or interconnect protocols.

In at least one embodiment, parallel processor(s) 2812 incorporate circuitry optimized for graphics and video processing, including, for example, video output circuitry, and constitutes a graphics processing unit (GPU). In at least one embodiment, parallel processor(s) 2812 incorporate circuitry optimized for general purpose processing. In at least embodiment, components of computing system 2800 may be integrated with one or more other system elements on a single integrated circuit. For example, in at least one embodiment, parallel processor(s) 2812, memory hub 2805, processor(s) 2802, and I/O hub 2807 can be integrated into a system on chip (SoC) integrated circuit. In at least one embodiment, components of computing system 2800 can be integrated into a single package to form a system in package (SIP) configuration. In at least one embodiment, at least a portion of components of computing system 2800 can be integrated into a multi-chip module (MCM), which can be interconnected with other multi-chip modules into a modular computing system.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in system FIG. 2800 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

Processors

FIG. 29A illustrates a parallel processor 2900 according to at least one embodiment. In at least one embodiment, various components of parallel processor 2900 may be implemented using one or more integrated circuit devices, such as programmable processors, application specific integrated circuits (ASICs), or field programmable gate arrays (FPGA). In at least one embodiment, illustrated parallel processor 2900 is a variant of one or more parallel processor(s) 2812 shown in FIG. 28 according to an exemplary embodiment.

In at least one embodiment, parallel processor 2900 includes a parallel processing unit 2902. In at least one embodiment, parallel processing unit 2902 includes an I/O unit 2904 that enables communication with other devices, including other instances of parallel processing unit 2902. In at least one embodiment, I/O unit 2904 may be directly connected to other devices. In at least one embodiment, I/O unit 2904 connects with other devices via use of a hub or switch interface, such as a memory hub 2905. In at least one embodiment, connections between memory hub 2905 and I/O unit 2904 form a communication link 2913. In at least one embodiment, I/O unit 2904 connects with a host interface 2906 and a memory crossbar 2916, where host interface 2906 receives commands directed to performing processing operations and memory crossbar 2916 receives commands directed to performing memory operations.

In at least one embodiment, when host interface 2906 receives a command buffer via I/O unit 2904, host interface 2906 can direct work operations to perform those commands to a front end 2908. In at least one embodiment, front end 2908 couples with a scheduler 2910, which is configured to distribute commands or other work items to a processing cluster array 2912. In at least one embodiment, scheduler 2910 ensures that processing cluster array 2912 is properly configured and in a valid state before tasks are distributed to a cluster of processing cluster array 2912. In at least one embodiment, scheduler 2910 is implemented via firmware logic executing on a microcontroller. In at least one embodiment, microcontroller implemented scheduler 2910 is configurable to perform complex scheduling and work distribution operations at coarse and fine granularity, enabling rapid preemption and context switching of threads executing on processing array 2912. In at least one embodiment, host software can prove workloads for scheduling on processing cluster array 2912 via one of multiple graphics processing paths. In at least one embodiment, workloads can then be automatically distributed across processing array cluster 2912 by scheduler 2910 logic within a microcontroller including scheduler 2910.

In at least one embodiment, processing cluster array 2912 can include up to “N” processing clusters (e.g., cluster 2914A, cluster 2914B, through cluster 2914N), where “N” represents a positive integer (which may be a different integer “N” than used in other figures). In at least one embodiment, each cluster 2914A-2914N of processing cluster array 2912 can execute a large number of concurrent threads. In at least one embodiment, scheduler 2910 can allocate work to clusters 2914A-2914N of processing cluster array 2912 using various scheduling and/or work distribution algorithms, which may vary depending on workload arising for each type of program or computation. In at least one embodiment, scheduling can be handled dynamically by scheduler 2910, or can be assisted in part by compiler logic during compilation of program logic configured for execution by processing cluster array 2912. In at least one embodiment, different clusters 2914A-2914N of processing cluster array 2912 can be allocated for processing different types of programs or for performing different types of computations.

In at least one embodiment, processing cluster array 2912 can be configured to perform various types of parallel processing operations. In at least one embodiment, processing cluster array 2912 is configured to perform general-purpose parallel compute operations. For example, in at least one embodiment, processing cluster array 2912 can include logic to execute processing tasks including filtering of video and/or audio data, performing modeling operations, including physics operations, and performing data transformations.

In at least one embodiment, processing cluster array 2912 is configured to perform parallel graphics processing operations. In at least one embodiment, processing cluster array 2912 can include additional logic to support execution of such graphics processing operations, including but not limited to, texture sampling logic to perform texture operations, as well as tessellation logic and other vertex processing logic. In at least one embodiment, processing cluster array 2912 can be configured to execute graphics processing related shader programs such as, but not limited to, vertex shaders, tessellation shaders, geometry shaders, and pixel shaders. In at least one embodiment, parallel processing unit 2902 can transfer data from system memory via I/O unit 2904 for processing. In at least one embodiment, during processing, transferred data can be stored to on-chip memory (e.g., parallel processor memory 2922) during processing, then written back to system memory.

In at least one embodiment, when parallel processing unit 2902 is used to perform graphics processing, scheduler 2910 can be configured to divide a processing workload into approximately equal sized tasks, to better enable distribution of graphics processing operations to multiple clusters 2914A-2914N of processing cluster array 2912. In at least one embodiment, portions of processing cluster array 2912 can be configured to perform different types of processing. For example, in at least one embodiment, a first portion may be configured to perform vertex shading and topology generation, a second portion may be configured to perform tessellation and geometry shading, and a third portion may be configured to perform pixel shading or other screen space operations, to produce a rendered image for display. In at least one embodiment, intermediate data produced by one or more of clusters 2914A-2914N may be stored in buffers to allow intermediate data to be transmitted between clusters 2914A-2914N for further processing.

In at least one embodiment, processing cluster array 2912 can receive processing tasks to be executed via scheduler 2910, which receives commands defining processing tasks from front end 2908. In at least one embodiment, processing tasks can include indices of data to be processed, e.g., surface (patch) data, primitive data, vertex data, and/or pixel data, as well as state parameters and commands defining how data is to be processed (e.g., what program is to be executed). In at least one embodiment, scheduler 2910 may be configured to fetch indices corresponding to tasks or may receive indices from front end 2908. In at least one embodiment, front end 2908 can be configured to ensure processing cluster array 2912 is configured to a valid state before a workload specified by incoming command buffers (e.g., batch-buffers, push buffers, etc.) is initiated.

In at least one embodiment, each of one or more instances of parallel processing unit 2902 can couple with a parallel processor memory 2922. In at least one embodiment, parallel processor memory 2922 can be accessed via memory crossbar 2916, which can receive memory requests from processing cluster array 2912 as well as I/O unit 2904. In at least one embodiment, memory crossbar 2916 can access parallel processor memory 2922 via a memory interface 2918. In at least one embodiment, memory interface 2918 can include multiple partition units (e.g., partition unit 2920A, partition unit 2920B, through partition unit 2920N) that can each couple to a portion (e.g., memory unit) of parallel processor memory 2922. In at least one embodiment, a number of partition units 2920A-2920N is configured to be equal to a number of memory units, such that a first partition unit 2920A has a corresponding first memory unit 2924A, a second partition unit 2920B has a corresponding memory unit 2924B, and an N-th partition unit 2920N has a corresponding N-th memory unit 2924N. In at least one embodiment, a number of partition units 2920A-2920N may not be equal to a number of memory units.

In at least one embodiment, memory units 2924A-2924N can include various types of memory devices, including dynamic random access memory (DRAM) or graphics random access memory, such as synchronous graphics random access memory (SGRAM), including graphics double data rate (GDDR) memory. In at least one embodiment, memory units 2924A-2924N may also include 3D stacked memory, including but not limited to high bandwidth memory (HBM). In at least one embodiment, render targets, such as frame buffers or texture maps may be stored across memory units 2924A-2924N, allowing partition units 2920A-2920N to write portions of each render target in parallel to efficiently use available bandwidth of parallel processor memory 2922. In at least one embodiment, a local instance of parallel processor memory 2922 may be excluded in favor of a unified memory design that utilizes system memory in conjunction with local cache memory.

In at least one embodiment, any one of clusters 2914A-2914N of processing cluster array 2912 can process data that will be written to any of memory units 2924A-2924N within parallel processor memory 2922. In at least one embodiment, memory crossbar 2916 can be configured to transfer an output of each cluster 2914A-2914N to any partition unit 2920A-2920N or to another cluster 2914A-2914N, which can perform additional processing operations on an output. In at least one embodiment, each cluster 2914A-2914N can communicate with memory interface 2918 through memory crossbar 2916 to read from or write to various external memory devices. In at least one embodiment, memory crossbar 2916 has a connection to memory interface 2918 to communicate with I/O unit 2904, as well as a connection to a local instance of parallel processor memory 2922, enabling processing units within different processing clusters 2914A-2914N to communicate with system memory or other memory that is not local to parallel processing unit 2902. In at least one embodiment, memory crossbar 2916 can use virtual channels to separate traffic streams between clusters 2914A-2914N and partition units 2920A-2920N.

In at least one embodiment, multiple instances of parallel processing unit 2902 can be provided on a single add-in card, or multiple add-in cards can be interconnected. In at least one embodiment, different instances of parallel processing unit 2902 can be configured to interoperate even if different instances have different numbers of processing cores, different amounts of local parallel processor memory, and/or other configuration differences. For example, in at least one embodiment, some instances of parallel processing unit 2902 can include higher precision floating point units relative to other instances. In at least one embodiment, systems incorporating one or more instances of parallel processing unit 2902 or parallel processor 2900 can be implemented in a variety of configurations and form factors, including but not limited to desktop, laptop, or handheld personal computers, servers, workstations, game consoles, and/or embedded systems.

FIG. 29B is a block diagram of a partition unit 2920 according to at least one embodiment. In at least one embodiment, partition unit 2920 is an instance of one of partition units 2920A-2920N of FIG. 29A. In at least one embodiment, partition unit 2920 includes an L2 cache 2921, a frame buffer interface 2925, and a ROP 2926 (raster operations unit). In at least one embodiment, L2 cache 2921 is a read/write cache that is configured to perform load and store operations received from memory crossbar 2916 and ROP 2926. In at least one embodiment, read misses and urgent write-back requests are output by L2 cache 2921 to frame buffer interface 2925 for processing. In at least one embodiment, updates can also be sent to a frame buffer via frame buffer interface 2925 for processing. In at least one embodiment, frame buffer interface 2925 interfaces with one of memory units in parallel processor memory, such as memory units 2924A-2924N of FIG. 29 (e.g., within parallel processor memory 2922).

In at least one embodiment, ROP 2926 is a processing unit that performs raster operations such as stencil, z test, blending, etc. In at least one embodiment, ROP 2926 then outputs processed graphics data that is stored in graphics memory. In at least one embodiment, ROP 2926 includes compression logic to compress depth or color data that is written to memory and decompress depth or color data that is read from memory. In at least one embodiment, compression logic can be lossless compression logic that makes use of one or more of multiple compression algorithms. In at least one embodiment, a type of compression that is performed by ROP 2926 can vary based on statistical characteristics of data to be compressed. For example, in at least one embodiment, delta color compression is performed on depth and color data on a per-tile basis.

In at least one embodiment, ROP 2926 is included within each processing cluster (e.g., cluster 2914A-2914N of FIG. 29A) instead of within partition unit 2920. In at least one embodiment, read and write requests for pixel data are transmitted over memory crossbar 2916 instead of pixel fragment data. In at least one embodiment, processed graphics data may be displayed on a display device, such as one of one or more display device(s) 2810 of FIG. 28 , routed for further processing by processor(s) 2802, or routed for further processing by one of processing entities within parallel processor 2900 of FIG. 29A.

FIG. 29C is a block diagram of a processing cluster 2914 within a parallel processing unit according to at least one embodiment. In at least one embodiment, a processing cluster is an instance of one of processing clusters 2914A-2914N of FIG. 29A. In at least one embodiment, processing cluster 2914 can be configured to execute many threads in parallel, where “thread” refers to an instance of a particular program executing on a particular set of input data. In at least one embodiment, single-instruction, multiple-data (SIMD) instruction issue techniques are used to support parallel execution of a large number of threads without providing multiple independent instruction units. In at least one embodiment, single-instruction, multiple-thread (SIMT) techniques are used to support parallel execution of a large number of generally synchronized threads, using a common instruction unit configured to issue instructions to a set of processing engines within each one of processing clusters.

In at least one embodiment, operation of processing cluster 2914 can be controlled via a pipeline manager 2932 that distributes processing tasks to SIMT parallel processors. In at least one embodiment, pipeline manager 2932 receives instructions from scheduler 2910 of FIG. 29A and manages execution of those instructions via a graphics multiprocessor 2934 and/or a texture unit 2936. In at least one embodiment, graphics multiprocessor 2934 is an exemplary instance of a SIMT parallel processor. However, in at least one embodiment, various types of SIMT parallel processors of differing architectures may be included within processing cluster 2914. In at least one embodiment, one or more instances of graphics multiprocessor 2934 can be included within a processing cluster 2914. In at least one embodiment, graphics multiprocessor 2934 can process data and a data crossbar 2940 can be used to distribute processed data to one of multiple possible destinations, including other shader units. In at least one embodiment, pipeline manager 2932 can facilitate distribution of processed data by specifying destinations for processed data to be distributed via data crossbar 2940.

In at least one embodiment, each graphics multiprocessor 2934 within processing cluster 2914 can include an identical set of functional execution logic (e.g., arithmetic logic units, load-store units, etc.). In at least one embodiment, functional execution logic can be configured in a pipelined manner in which new instructions can be issued before previous instructions are complete. In at least one embodiment, functional execution logic supports a variety of operations including integer and floating point arithmetic, comparison operations, Boolean operations, bit-shifting, and computation of various algebraic functions. In at least one embodiment, same functional-unit hardware can be leveraged to perform different operations and any combination of functional units may be present.

In at least one embodiment, instructions transmitted to processing cluster 2914 constitute a thread. In at least one embodiment, a set of threads executing across a set of parallel processing engines is a thread group. In at least one embodiment, a thread group executes a common program on different input data. In at least one embodiment, each thread within a thread group can be assigned to a different processing engine within a graphics multiprocessor 2934. In at least one embodiment, a thread group may include fewer threads than a number of processing engines within graphics multiprocessor 2934. In at least one embodiment, when a thread group includes fewer threads than a number of processing engines, one or more of processing engines may be idle during cycles in which that thread group is being processed. In at least one embodiment, a thread group may also include more threads than a number of processing engines within graphics multiprocessor 2934. In at least one embodiment, when a thread group includes more threads than number of processing engines within graphics multiprocessor 2934, processing can be performed over consecutive clock cycles. In at least one embodiment, multiple thread groups can be executed concurrently on a graphics multiprocessor 2934.

In at least one embodiment, graphics multiprocessor 2934 includes an internal cache memory to perform load and store operations. In at least one embodiment, graphics multiprocessor 2934 can forego an internal cache and use a cache memory (e.g., L1 cache 2948) within processing cluster 2914. In at least one embodiment, each graphics multiprocessor 2934 also has access to L2 caches within partition units (e.g., partition units 2920A-2920N of FIG. 29A) that are shared among all processing clusters 2914 and may be used to transfer data between threads. In at least one embodiment, graphics multiprocessor 2934 may also access off-chip global memory, which can include one or more of local parallel processor memory and/or system memory. In at least one embodiment, any memory external to parallel processing unit 2902 may be used as global memory. In at least one embodiment, processing cluster 2914 includes multiple instances of graphics multiprocessor 2934 and can share common instructions and data, which may be stored in L1 cache 2948.

In at least one embodiment, each processing cluster 2914 may include an MMU 2945 (memory management unit) that is configured to map virtual addresses into physical addresses. In at least one embodiment, one or more instances of MMU 2945 may reside within memory interface 2918 of FIG. 29A. In at least one embodiment, MMU 2945 includes a set of page table entries (PTEs) used to map a virtual address to a physical address of a tile and optionally a cache line index. In at least one embodiment, MMU 2945 may include address translation lookaside buffers (TLB) or caches that may reside within graphics multiprocessor 2934 or L1 2948 cache or processing cluster 2914. In at least one embodiment, a physical address is processed to distribute surface data access locally to allow for efficient request interleaving among partition units. In at least one embodiment, a cache line index may be used to determine whether a request for a cache line is a hit or miss.

In at least one embodiment, a processing cluster 2914 may be configured such that each graphics multiprocessor 2934 is coupled to a texture unit 2936 for performing texture mapping operations, e.g., determining texture sample positions, reading texture data, and filtering texture data. In at least one embodiment, texture data is read from an internal texture L1 cache (not shown) or from an L1 cache within graphics multiprocessor 2934 and is fetched from an L2 cache, local parallel processor memory, or system memory, as needed. In at least one embodiment, each graphics multiprocessor 2934 outputs processed tasks to data crossbar 2940 to provide processed task to another processing cluster 2914 for further processing or to store processed task in an L2 cache, local parallel processor memory, or system memory via memory crossbar 2916. In at least one embodiment, a preROP 2942 (pre-raster operations unit) is configured to receive data from graphics multiprocessor 2934, and direct data to ROP units, which may be located with partition units as described herein (e.g., partition units 2920A-2920N of FIG. 29A). In at least one embodiment, preROP 2942 unit can perform optimizations for color blending, organizing pixel color data, and performing address translations.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in graphics processing cluster 2914 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 29D shows a graphics multiprocessor 2934 according to at least one embodiment. In at least one embodiment, graphics multiprocessor 2934 couples with pipeline manager 2932 of processing cluster 2914. In at least one embodiment, graphics multiprocessor 2934 has an execution pipeline including but not limited to an instruction cache 2952, an instruction unit 2954, an address mapping unit 2956, a register file 2958, one or more general purpose graphics processing unit (GPGPU) cores 2962, and one or more load/store units 2966. In at least one embodiment, GPGPU cores 2962 and load/store units 2966 are coupled with cache memory 2972 and shared memory 2970 via a memory and cache interconnect 2968.

In at least one embodiment, instruction cache 2952 receives a stream of instructions to execute from pipeline manager 2932. In at least one embodiment, instructions are cached in instruction cache 2952 and dispatched for execution by an instruction unit 2954. In at least one embodiment, instruction unit 2954 can dispatch instructions as thread groups (e.g., warps), with each thread of thread group assigned to a different execution unit within GPGPU cores 2962. In at least one embodiment, an instruction can access any of a local, shared, or global address space by specifying an address within a unified address space. In at least one embodiment, address mapping unit 2956 can be used to translate addresses in a unified address space into a distinct memory address that can be accessed by load/store units 2966.

In at least one embodiment, register file 2958 provides a set of registers for functional units of graphics multiprocessor 2934. In at least one embodiment, register file 2958 provides temporary storage for operands connected to data paths of functional units (e.g., GPGPU cores 2962, load/store units 2966) of graphics multiprocessor 2934. In at least one embodiment, register file 2958 is divided between each of functional units such that each functional unit is allocated a dedicated portion of register file 2958. In at least one embodiment, register file 2958 is divided between different warps being executed by graphics multiprocessor 2934.

In at least one embodiment, GPGPU cores 2962 can each include floating point units (FPUs) and/or integer arithmetic logic units (ALUs) that are used to execute instructions of graphics multiprocessor 2934. In at least one embodiment, GPGPU cores 2962 can be similar in architecture or can differ in architecture. In at least one embodiment, a first portion of GPGPU cores 2962 include a single precision FPU and an integer ALU while a second portion of GPGPU cores include a double precision FPU. In at least one embodiment, FPUs can implement IEEE 754-2008 standard floating point arithmetic or enable variable precision floating point arithmetic. In at least one embodiment, graphics multiprocessor 2934 can additionally include one or more fixed function or special function units to perform specific functions such as copy rectangle or pixel blending operations. In at least one embodiment, one or more of GPGPU cores 2962 can also include fixed or special function logic.

In at least one embodiment, GPGPU cores 2962 include SIMD logic capable of performing a single instruction on multiple sets of data. In at least one embodiment, GPGPU cores 2962 can physically execute SIMD4, SIMD8, and SIMD16 instructions and logically execute SIMD1, SIMD2, and SIMD32 instructions. In at least one embodiment, SIMD instructions for GPGPU cores can be generated at compile time by a shader compiler or automatically generated when executing programs written and compiled for single program multiple data (SPMD) or SIMT architectures. In at least one embodiment, multiple threads of a program configured for an SIMT execution model can executed via a single SIMD instruction. For example, in at least one embodiment, eight SIMT threads that perform same or similar operations can be executed in parallel via a single SIMD8 logic unit.

In at least one embodiment, memory and cache interconnect 2968 is an interconnect network that connects each functional unit of graphics multiprocessor 2934 to register file 2958 and to shared memory 2970. In at least one embodiment, memory and cache interconnect 2968 is a crossbar interconnect that allows load/store unit 2966 to implement load and store operations between shared memory 2970 and register file 2958. In at least one embodiment, register file 2958 can operate at a same frequency as GPGPU cores 2962, thus data transfer between GPGPU cores 2962 and register file 2958 can have very low latency. In at least one embodiment, shared memory 2970 can be used to enable communication between threads that execute on functional units within graphics multiprocessor 2934. In at least one embodiment, cache memory 2972 can be used as a data cache for example, to cache texture data communicated between functional units and texture unit 2936. In at least one embodiment, shared memory 2970 can also be used as a program managed cache. In at least one embodiment, threads executing on GPGPU cores 2962 can programmatically store data within shared memory in addition to automatically cached data that is stored within cache memory 2972.

In at least one embodiment, a parallel processor or GPGPU as described herein is communicatively coupled to host/processor cores to accelerate graphics operations, machine-learning operations, pattern analysis operations, and various general purpose GPU (GPGPU) functions. In at least one embodiment, a GPU may be communicatively coupled to host processor/cores over a bus or other interconnect (e.g., a high-speed interconnect such as PCIe or NVLink). In at least one embodiment, a GPU may be integrated on a package or chip as cores and communicatively coupled to cores over an internal processor bus/interconnect internal to a package or chip. In at least one embodiment, regardless a manner in which a GPU is connected, processor cores may allocate work to such GPU in a form of sequences of commands/instructions contained in a work descriptor. In at least one embodiment, that GPU then uses dedicated circuitry/logic for efficiently processing these commands/instructions.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in graphics multiprocessor 2934 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 30 illustrates a multi-GPU computing system 3000, according to at least one embodiment. In at least one embodiment, multi-GPU computing system 3000 can include a processor 3002 coupled to multiple general purpose graphics processing units (GPGPUs) 3006A-D via a host interface switch 3004. In at least one embodiment, host interface switch 3004 is a PCI express switch device that couples processor 3002 to a PCI express bus over which processor 3002 can communicate with GPGPUs 3006A-D. In at least one embodiment, GPGPUs 3006A-D can interconnect via a set of high-speed point-to-point GPU-to-GPU links 3016. In at least one embodiment, GPU-to-GPU links 3016 connect to each of GPGPUs 3006A-D via a dedicated GPU link. In at least one embodiment, P2P GPU links 3016 enable direct communication between each of GPGPUs 3006A-D without requiring communication over host interface bus 3004 to which processor 3002 is connected. In at least one embodiment, with GPU-to-GPU traffic directed to P2P GPU links 3016, host interface bus 3004 remains available for system memory access or to communicate with other instances of multi-GPU computing system 3000, for example, via one or more network devices. While in at least one embodiment GPGPUs 3006A-D connect to processor 3002 via host interface switch 3004, in at least one embodiment processor 3002 includes direct support for P2P GPU links 3016 and can connect directly to GPGPUs 3006A-D.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in multi-GPU computing system 3000 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 31 is a block diagram of a graphics processor 3100, according to at least one embodiment. In at least one embodiment, graphics processor 3100 includes a ring interconnect 3102, a pipeline front-end 3104, a media engine 3137, and graphics cores 3180A-3180N. In at least one embodiment, ring interconnect 3102 couples graphics processor 3100 to other processing units, including other graphics processors or one or more general-purpose processor cores. In at least one embodiment, graphics processor 3100 is one of many processors integrated within a multi-core processing system.

In at least one embodiment, graphics processor 3100 receives batches of commands via ring interconnect 3102. In at least one embodiment, incoming commands are interpreted by a command streamer 3103 in pipeline front-end 3104. In at least one embodiment, graphics processor 3100 includes scalable execution logic to perform 3D geometry processing and media processing via graphics core(s) 3180A-3180N. In at least one embodiment, for 3D geometry processing commands, command streamer 3103 supplies commands to geometry pipeline 3136. In at least one embodiment, for at least some media processing commands, command streamer 3103 supplies commands to a video front end 3134, which couples with media engine 3137. In at least one embodiment, media engine 3137 includes a Video Quality Engine (VQE) 3130 for video and image post-processing and a multi-format encode/decode (MFX) 3133 engine to provide hardware-accelerated media data encoding and decoding. In at least one embodiment, geometry pipeline 3136 and media engine 3137 each generate execution threads for thread execution resources provided by at least one graphics core 3180.

In at least one embodiment, graphics processor 3100 includes scalable thread execution resources featuring graphics cores 3180A-3180N (which can be modular and are sometimes referred to as core slices), each having multiple sub-cores 3150A-50N, 3160A-3160N (sometimes referred to as core sub-slices). In at least one embodiment, graphics processor 3100 can have any number of graphics cores 3180A. In at least one embodiment, graphics processor 3100 includes a graphics core 3180A having at least a first sub-core 3150A and a second sub-core 3160A. In at least one embodiment, graphics processor 3100 is a low power processor with a single sub-core (e.g., 3150A). In at least one embodiment, graphics processor 3100 includes multiple graphics cores 3180A-3180N, each including a set of first sub-cores 3150A-3150N and a set of second sub-cores 3160A-3160N. In at least one embodiment, each sub-core in first sub-cores 3150A-3150N includes at least a first set of execution units 3152A-3152N and media/texture samplers 3154A-3154N. In at least one embodiment, each sub-core in second sub-cores 3160A-3160N includes at least a second set of execution units 3162A-3162N and samplers 3164A-3164N. In at least one embodiment, each sub-core 3150A-3150N, 3160A-3160N shares a set of shared resources 3170A-3170N. In at least one embodiment, shared resources include shared cache memory and pixel operation logic.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, inference and/or training logic 1615 may be used in graphics processor 3100 for inferencing or predicting operations based, at least in part, on weight parameters calculated using neural network training operations, neural network functions and/or architectures, or neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 32 is a block diagram illustrating micro-architecture for a processor 3200 that may include logic circuits to perform instructions, according to at least one embodiment. In at least one embodiment, processor 3200 may perform instructions, including x86 instructions, ARM instructions, specialized instructions for application-specific integrated circuits (ASICs), etc. In at least one embodiment, processor 3200 may include registers to store packed data, such as 64-bit wide MMX™ registers in microprocessors enabled with MMX technology from Intel Corporation of Santa Clara, Calif. In at least one embodiment, MMX registers, available in both integer and floating point forms, may operate with packed data elements that accompany single instruction, multiple data (“SIMD”) and streaming SIMD extensions (“SSE”) instructions. In at least one embodiment, 128-bit wide XMM registers relating to SSE2, SSE3, SSE4, AVX, or beyond (referred to generically as “SSEx”) technology may hold such packed data operands. In at least one embodiment, processor 3200 may perform instructions to accelerate machine learning or deep learning algorithms, training, or inferencing.

In at least one embodiment, processor 3200 includes an in-order front end (“front end”) 3201 to fetch instructions to be executed and prepare instructions to be used later in a processor pipeline. In at least one embodiment, front end 3201 may include several units. In at least one embodiment, an instruction prefetcher 3226 fetches instructions from memory and feeds instructions to an instruction decoder 3228 which in turn decodes or interprets instructions. For example, in at least one embodiment, instruction decoder 3228 decodes a received instruction into one or more operations called “micro-instructions” or “micro-operations” (also called “micro ops” or “uops”) that a machine may execute. In at least one embodiment, instruction decoder 3228 parses an instruction into an opcode and corresponding data and control fields that may be used by micro-architecture to perform operations in accordance with at least one embodiment. In at least one embodiment, a trace cache 3230 may assemble decoded uops into program ordered sequences or traces in a uop queue 3234 for execution. In at least one embodiment, when trace cache 3230 encounters a complex instruction, a microcode ROM 3232 provides uops needed to complete an operation.

In at least one embodiment, some instructions may be converted into a single micro-op, whereas others need several micro-ops to complete full operation. In at least one embodiment, if more than four micro-ops are needed to complete an instruction, instruction decoder 3228 may access microcode ROM 3232 to perform that instruction. In at least one embodiment, an instruction may be decoded into a small number of micro-ops for processing at instruction decoder 3228. In at least one embodiment, an instruction may be stored within microcode ROM 3232 should a number of micro-ops be needed to accomplish such operation. In at least one embodiment, trace cache 3230 refers to an entry point programmable logic array (“PLA”) to determine a correct micro-instruction pointer for reading microcode sequences to complete one or more instructions from microcode ROM 3232 in accordance with at least one embodiment. In at least one embodiment, after microcode ROM 3232 finishes sequencing micro-ops for an instruction, front end 3201 of a machine may resume fetching micro-ops from trace cache 3230.

In at least one embodiment, out-of-order execution engine (“out of order engine”) 3203 may prepare instructions for execution. In at least one embodiment, out-of-order execution logic has a number of buffers to smooth out and re-order flow of instructions to optimize performance as they go down a pipeline and get scheduled for execution. In at least one embodiment, out-of-order execution engine 3203 includes, without limitation, an allocator/register renamer 3240, a memory uop queue 3242, an integer/floating point uop queue 3244, a memory scheduler 3246, a fast scheduler 3202, a slow/general floating point scheduler (“slow/general FP scheduler”) 3204, and a simple floating point scheduler (“simple FP scheduler”) 3206. In at least one embodiment, fast schedule 3202, slow/general floating point scheduler 3204, and simple floating point scheduler 3206 are also collectively referred to herein as “uop schedulers 3202, 3204, 3206.” In at least one embodiment, allocator/register renamer 3240 allocates machine buffers and resources that each uop needs in order to execute. In at least one embodiment, allocator/register renamer 3240 renames logic registers onto entries in a register file. In at least one embodiment, allocator/register renamer 3240 also allocates an entry for each uop in one of two uop queues, memory uop queue 3242 for memory operations and integer/floating point uop queue 3244 for non-memory operations, in front of memory scheduler 3246 and uop schedulers 3202, 3204, 3206. In at least one embodiment, uop schedulers 3202, 3204, 3206, determine when a uop is ready to execute based on readiness of their dependent input register operand sources and availability of execution resources uops need to complete their operation. In at least one embodiment, fast scheduler 3202 may schedule on each half of a main clock cycle while slow/general floating point scheduler 3204 and simple floating point scheduler 3206 may schedule once per main processor clock cycle. In at least one embodiment, uop schedulers 3202, 3204, 3206 arbitrate for dispatch ports to schedule uops for execution.

In at least one embodiment, execution block 3211 includes, without limitation, an integer register file/bypass network 3208, a floating point register file/bypass network (“FP register file/bypass network”) 3210, address generation units (“AGUs”) 3212 and 3214, fast Arithmetic Logic Units (ALUs) (“fast ALUs”) 3216 and 3218, a slow Arithmetic Logic Unit (“slow ALU”) 3220, a floating point ALU (“FP”) 3222, and a floating point move unit (“FP move”) 3224. In at least one embodiment, integer register file/bypass network 3208 and floating point register file/bypass network 3210 are also referred to herein as “register files 3208, 3210.” In at least one embodiment, AGUSs 3212 and 3214, fast ALUs 3216 and 3218, slow ALU 3220, floating point ALU 3222, and floating point move unit 3224 are also referred to herein as “execution units 3212, 3214, 3216, 3218, 3220, 3222, and 3224.” In at least one embodiment, execution block 3211 may include, without limitation, any number (including zero) and type of register files, bypass networks, address generation units, and execution units, in any combination.

In at least one embodiment, register networks 3208, 3210 may be arranged between uop schedulers 3202, 3204, 3206, and execution units 3212, 3214, 3216, 3218, 3220, 3222, and 3224. In at least one embodiment, integer register file/bypass network 3208 performs integer operations. In at least one embodiment, floating point register file/bypass network 3210 performs floating point operations. In at least one embodiment, each of register networks 3208, 3210 may include, without limitation, a bypass network that may bypass or forward just completed results that have not yet been written into a register file to new dependent uops. In at least one embodiment, register networks 3208, 3210 may communicate data with each other. In at least one embodiment, integer register file/bypass network 3208 may include, without limitation, two separate register files, one register file for a low-order thirty-two bits of data and a second register file for a high order thirty-two bits of data. In at least one embodiment, floating point register file/bypass network 3210 may include, without limitation, 128-bit wide entries because floating point instructions typically have operands from 64 to 128 bits in width.

In at least one embodiment, execution units 3212, 3214, 3216, 3218, 3220, 3222, 3224 may execute instructions. In at least one embodiment, register networks 3208, 3210 store integer and floating point data operand values that micro-instructions need to execute. In at least one embodiment, processor 3200 may include, without limitation, any number and combination of execution units 3212, 3214, 3216, 3218, 3220, 3222, 3224. In at least one embodiment, floating point ALU 3222 and floating point move unit 3224, may execute floating point, MMX, SIMD, AVX and SSE, or other operations, including specialized machine learning instructions. In at least one embodiment, floating point ALU 3222 may include, without limitation, a 64-bit by 64-bit floating point divider to execute divide, square root, and remainder micro ops. In at least one embodiment, instructions involving a floating point value may be handled with floating point hardware. In at least one embodiment, ALU operations may be passed to fast ALUs 3216, 3218. In at least one embodiment, fast ALUS 3216, 3218 may execute fast operations with an effective latency of half a clock cycle. In at least one embodiment, most complex integer operations go to slow ALU 3220 as slow ALU 3220 may include, without limitation, integer execution hardware for long-latency type of operations, such as a multiplier, shifts, flag logic, and branch processing. In at least one embodiment, memory load/store operations may be executed by AGUs 3212, 3214. In at least one embodiment, fast ALU 3216, fast ALU 3218, and slow ALU 3220 may perform integer operations on 64-bit data operands. In at least one embodiment, fast ALU 3216, fast ALU 3218, and slow ALU 3220 may be implemented to support a variety of data bit sizes including sixteen, thirty-two, 128, 256, etc. In at least one embodiment, floating point ALU 3222 and floating point move unit 3224 may be implemented to support a range of operands having bits of various widths, such as 128-bit wide packed data operands in conjunction with SIMD and multimedia instructions.

In at least one embodiment, uop schedulers 3202, 3204, 3206 dispatch dependent operations before a parent load has finished executing. In at least one embodiment, as uops may be speculatively scheduled and executed in processor 3200, processor 3200 may also include logic to handle memory misses. In at least one embodiment, if a data load misses in a data cache, there may be dependent operations in flight in a pipeline that have left a scheduler with temporarily incorrect data. In at least one embodiment, a replay mechanism tracks and re-executes instructions that use incorrect data. In at least one embodiment, dependent operations might need to be replayed and independent ones may be allowed to complete. In at least one embodiment, schedulers and a replay mechanism of at least one embodiment of a processor may also be designed to catch instruction sequences for text string comparison operations.

In at least one embodiment, “registers” may refer to on-board processor storage locations that may be used as part of instructions to identify operands. In at least one embodiment, registers may be those that may be usable from outside of a processor (from a programmer's perspective). In at least one embodiment, registers might not be limited to a particular type of circuit. Rather, in at least one embodiment, a register may store data, provide data, and perform functions described herein. In at least one embodiment, registers described herein may be implemented by circuitry within a processor using any number of different techniques, such as dedicated physical registers, dynamically allocated physical registers using register renaming, combinations of dedicated and dynamically allocated physical registers, etc. In at least one embodiment, integer registers store 32-bit integer data. A register file of at least one embodiment also contains eight multimedia SIMD registers for packed data.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment portions or all of inference and/or training logic 1615 may be incorporated into execution block 3211 and other memory or registers shown or not shown. For example, in at least one embodiment, training and/or inferencing techniques described herein may use one or more of ALUs illustrated in execution block 3211. Moreover, weight parameters may be stored in on-chip or off-chip memory and/or registers (shown or not shown) that configure ALUs of execution block 3211 to perform one or more machine learning algorithms, neural network architectures, use cases, or training techniques described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 33 illustrates a deep learning application processor 3300, according to at least one embodiment. In at least one embodiment, deep learning application processor 3300 uses instructions that, if executed by deep learning application processor 3300, cause deep learning application processor 3300 to perform some or all of processes and techniques described throughout this disclosure. In at least one embodiment, deep learning application processor 3300 is an application-specific integrated circuit (ASIC). In at least one embodiment, application processor 3300 performs matrix multiply operations either “hard-wired” into hardware as a result of performing one or more instructions or both. In at least one embodiment, deep learning application processor 3300 includes, without limitation, processing clusters 3310(1)-3310(12), Inter-Chip Links (“ICLs”) 3320(1)-3320(12), Inter-Chip Controllers (“ICCs”) 3330(1)-3330(2), high-bandwidth memory second generation (“HBM2”) 3340(1)-3340(4), memory controllers (“Mem Ctrlrs”) 3342(1)-3342(4), high bandwidth memory physical layer (“HBM PHY”) 3344(1)-3344(4), a management-controller central processing unit (“management-controller CPU”) 3350, a Serial Peripheral Interface, Inter-Integrated Circuit, and General Purpose Input/Output block (“SPI, I²C, GPIO”) 3360, a peripheral component interconnect express controller and direct memory access block (“PCIe Controller and DMA”) 3370, and a sixteen-lane peripheral component interconnect express port (“PCI Express×16”) 3380.

In at least one embodiment, processing clusters 3310 may perform deep learning operations, including inference or prediction operations based on weight parameters calculated one or more training techniques, including those described herein. In at least one embodiment, each processing cluster 3310 may include, without limitation, any number and type of processors. In at least one embodiment, deep learning application processor 3300 may include any number and type of processing clusters 3300. In at least one embodiment, Inter-Chip Links 3320 are bi-directional. In at least one embodiment, Inter-Chip Links 3320 and Inter-Chip Controllers 3330 enable multiple deep learning application processors 3300 to exchange information, including activation information resulting from performing one or more machine learning algorithms embodied in one or more neural networks. In at least one embodiment, deep learning application processor 3300 may include any number (including zero) and type of ICLs 3320 and ICCs 3330.

In at least one embodiment, HBM2s 3340 provide a total of 32 Gigabytes (GB) of memory. In at least one embodiment, HBM2 3340(i) is associated with both memory controller 3342(i) and HBM PHY 3344(i) where “i” is an arbitrary integer. In at least one embodiment, any number of HBM2s 3340 may provide any type and total amount of high bandwidth memory and may be associated with any number (including zero) and type of memory controllers 3342 and HBM PHYs 3344. In at least one embodiment, SPI, I²C, GPIO 3360, PCIe Controller and DMA 3370, and/or PCIe 3380 may be replaced with any number and type of blocks that enable any number and type of communication standards in any technically feasible fashion.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, deep learning application processor is used to train a machine learning model, such as a neural network, to predict or infer information provided to deep learning application processor 3300. In at least one embodiment, deep learning application processor 3300 is used to infer or predict information based on a trained machine learning model (e.g., neural network) that has been trained by another processor or system or by deep learning application processor 3300. In at least one embodiment, processor 3300 may be used to perform one or more neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 34 is a block diagram of a neuromorphic processor 3400, according to at least one embodiment. In at least one embodiment, neuromorphic processor 3400 may receive one or more inputs from sources external to neuromorphic processor 3400. In at least one embodiment, these inputs may be transmitted to one or more neurons 3402 within neuromorphic processor 3400. In at least one embodiment, neurons 3402 and components thereof may be implemented using circuitry or logic, including one or more arithmetic logic units (ALUs). In at least one embodiment, neuromorphic processor 3400 may include, without limitation, thousands or millions of instances of neurons 3402, but any suitable number of neurons 3402 may be used. In at least one embodiment, each instance of neuron 3402 may include a neuron input 3404 and a neuron output 3406. In at least one embodiment, neurons 3402 may generate outputs that may be transmitted to inputs of other instances of neurons 3402. For example, in at least one embodiment, neuron inputs 3404 and neuron outputs 3406 may be interconnected via synapses 3408.

In at least one embodiment, neurons 3402 and synapses 3408 may be interconnected such that neuromorphic processor 3400 operates to process or analyze information received by neuromorphic processor 3400. In at least one embodiment, neurons 3402 may transmit an output pulse (or “fire” or “spike”) when inputs received through neuron input 3404 exceed a threshold. In at least one embodiment, neurons 3402 may sum or integrate signals received at neuron inputs 3404. For example, in at least one embodiment, neurons 3402 may be implemented as leaky integrate-and-fire neurons, wherein if a sum (referred to as a “membrane potential”) exceeds a threshold value, neuron 3402 may generate an output (or “fire”) using a transfer function such as a sigmoid or threshold function. In at least one embodiment, a leaky integrate-and-fire neuron may sum signals received at neuron inputs 3404 into a membrane potential and may also apply a decay factor (or leak) to reduce a membrane potential. In at least one embodiment, a leaky integrate-and-fire neuron may fire if multiple input signals are received at neuron inputs 3404 rapidly enough to exceed a threshold value (i.e., before a membrane potential decays too low to fire). In at least one embodiment, neurons 3402 may be implemented using circuits or logic that receive inputs, integrate inputs into a membrane potential, and decay a membrane potential. In at least one embodiment, inputs may be averaged, or any other suitable transfer function may be used. Furthermore, in at least one embodiment, neurons 3402 may include, without limitation, comparator circuits or logic that generate an output spike at neuron output 3406 when result of applying a transfer function to neuron input 3404 exceeds a threshold. In at least one embodiment, once neuron 3402 fires, it may disregard previously received input information by, for example, resetting a membrane potential to 0 or another suitable default value. In at least one embodiment, once membrane potential is reset to 0, neuron 3402 may resume normal operation after a suitable period of time (or refractory period).

In at least one embodiment, neurons 3402 may be interconnected through synapses 3408. In at least one embodiment, synapses 3408 may operate to transmit signals from an output of a first neuron 3402 to an input of a second neuron 3402. In at least one embodiment, neurons 3402 may transmit information over more than one instance of synapse 3408. In at least one embodiment, one or more instances of neuron output 3406 may be connected, via an instance of synapse 3408, to an instance of neuron input 3404 in same neuron 3402. In at least one embodiment, an instance of neuron 3402 generating an output to be transmitted over an instance of synapse 3408 may be referred to as a “pre-synaptic neuron” with respect to that instance of synapse 3408. In at least one embodiment, an instance of neuron 3402 receiving an input transmitted over an instance of synapse 3408 may be referred to as a “post-synaptic neuron” with respect to that instance of synapse 3408. Because an instance of neuron 3402 may receive inputs from one or more instances of synapse 3408, and may also transmit outputs over one or more instances of synapse 3408, a single instance of neuron 3402 may therefore be both a “pre-synaptic neuron” and “post-synaptic neuron,” with respect to various instances of synapses 3408, in at least one embodiment.

In at least one embodiment, neurons 3402 may be organized into one or more layers. In at least one embodiment, each instance of neuron 3402 may have one neuron output 3406 that may fan out through one or more synapses 3408 to one or more neuron inputs 3404. In at least one embodiment, neuron outputs 3406 of neurons 3402 in a first layer 3410 may be connected to neuron inputs 3404 of neurons 3402 in a second layer 3412. In at least one embodiment, layer 3410 may be referred to as a “feed-forward layer.” In at least one embodiment, each instance of neuron 3402 in an instance of first layer 3410 may fan out to each instance of neuron 3402 in second layer 3412. In at least one embodiment, first layer 3410 may be referred to as a “fully connected feed-forward layer.” In at least one embodiment, each instance of neuron 3402 in an instance of second layer 3412 may fan out to fewer than all instances of neuron 3402 in a third layer 3414. In at least one embodiment, second layer 3412 may be referred to as a “sparsely connected feed-forward layer.” In at least one embodiment, neurons 3402 in second layer 3412 may fan out to neurons 3402 in multiple other layers, including to neurons 3402 also in second layer 3412. In at least one embodiment, second layer 3412 may be referred to as a “recurrent layer.” In at least one embodiment, neuromorphic processor 3400 may include, without limitation, any suitable combination of recurrent layers and feed-forward layers, including, without limitation, both sparsely connected feed-forward layers and fully connected feed-forward layers.

In at least one embodiment, neuromorphic processor 3400 may include, without limitation, a reconfigurable interconnect architecture or dedicated hard-wired interconnects to connect synapse 3408 to neurons 3402. In at least one embodiment, neuromorphic processor 3400 may include, without limitation, circuitry or logic that allows synapses to be allocated to different neurons 3402 as needed based on neural network topology and neuron fan-in/out. For example, in at least one embodiment, synapses 3408 may be connected to neurons 3402 using an interconnect fabric, such as network-on-chip, or with dedicated connections. In at least one embodiment, synapse interconnections and components thereof may be implemented using circuitry or logic.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 35 is a block diagram of a processing system, according to at least one embodiment. In at least one embodiment, system 3500 includes one or more processors 3502 and one or more graphics processors 3508, and may be a single processor desktop system, a multiprocessor workstation system, or a server system having a large number of processors 3502 or processor cores 3507. In at least one embodiment, system 3500 is a processing platform incorporated within a system-on-a-chip (SoC) integrated circuit for use in mobile, handheld, or embedded devices.

In at least one embodiment, system 3500 can include, or be incorporated within a server-based gaming platform, a game console, including a game and media console, a mobile gaming console, a handheld game console, or an online game console. In at least one embodiment, system 3500 is a mobile phone, a smart phone, a tablet computing device or a mobile Internet device. In at least one embodiment, processing system 3500 can also include, couple with, or be integrated within a wearable device, such as a smart watch wearable device, a smart eyewear device, an augmented reality device, or a virtual reality device. In at least one embodiment, processing system 3500 is a television or set top box device having one or more processors 3502 and a graphical interface generated by one or more graphics processors 3508.

In at least one embodiment, one or more processors 3502 each include one or more processor cores 3507 to process instructions which, when executed, perform operations for system and user software. In at least one embodiment, each of one or more processor cores 3507 is configured to process a specific instruction sequence 3509. In at least one embodiment, instruction sequence 3509 may facilitate Complex Instruction Set Computing (CISC), Reduced Instruction Set Computing (RISC), or computing via a Very Long Instruction Word (VLIW). In at least one embodiment, processor cores 3507 may each process a different instruction sequence 3509, which may include instructions to facilitate emulation of other instruction sequences. In at least one embodiment, processor core 3507 may also include other processing devices, such a Digital Signal Processor (DSP).

In at least one embodiment, processor 3502 includes a cache memory 3504. In at least one embodiment, processor 3502 can have a single internal cache or multiple levels of internal cache. In at least one embodiment, cache memory is shared among various components of processor 3502. In at least one embodiment, processor 3502 also uses an external cache (e.g., a Level-3 (L3) cache or Last Level Cache (LLC)) (not shown), which may be shared among processor cores 3507 using known cache coherency techniques. In at least one embodiment, a register file 3506 is additionally included in processor 3502, which may include different types of registers for storing different types of data (e.g., integer registers, floating point registers, status registers, and an instruction pointer register). In at least one embodiment, register file 3506 may include general-purpose registers or other registers.

In at least one embodiment, one or more processor(s) 3502 are coupled with one or more interface bus(es) 3510 to transmit communication signals such as address, data, or control signals between processor 3502 and other components in system 3500. In at least one embodiment, interface bus 3510, in one embodiment, can be a processor bus, such as a version of a Direct Media Interface (DMI) bus. In at least one embodiment, interface bus 3510 is not limited to a DMI bus, and may include one or more Peripheral Component Interconnect buses (e.g., PCI, PCI Express), memory busses, or other types of interface busses. In at least one embodiment processor(s) 3502 include an integrated memory controller 3516 and a platform controller hub 3530. In at least one embodiment, memory controller 3516 facilitates communication between a memory device and other components of system 3500, while platform controller hub (PCH) 3530 provides connections to I/O devices via a local I/O bus.

In at least one embodiment, a memory device 3520 can be a dynamic random access memory (DRAM) device, a static random access memory (SRAM) device, flash memory device, phase-change memory device, or some other memory device having suitable performance to serve as process memory. In at least one embodiment, memory device 3520 can operate as system memory for system 3500, to store data 3522 and instructions 3521 for use when one or more processors 3502 executes an application or process. In at least one embodiment, memory controller 3516 also couples with an optional external graphics processor 3512, which may communicate with one or more graphics processors 3508 in processors 3502 to perform graphics and media operations. In at least one embodiment, a display device 3511 can connect to processor(s) 3502. In at least one embodiment, display device 3511 can include one or more of an internal display device, as in a mobile electronic device or a laptop device, or an external display device attached via a display interface (e.g., DisplayPort, etc.). In at least one embodiment, display device 3511 can include a head mounted display (HMD) such as a stereoscopic display device for use in virtual reality (VR) applications or augmented reality (AR) applications.

In at least one embodiment, platform controller hub 3530 enables peripherals to connect to memory device 3520 and processor 3502 via a high-speed I/O bus. In at least one embodiment, I/O peripherals include, but are not limited to, an audio controller 3546, a network controller 3534, a firmware interface 3528, a wireless transceiver 3526, touch sensors 3525, a data storage device 3524 (e.g., hard disk drive, flash memory, etc.). In at least one embodiment, data storage device 3524 can connect via a storage interface (e.g., SATA) or via a peripheral bus, such as a Peripheral Component Interconnect bus (e.g., PCI, PCI Express). In at least one embodiment, touch sensors 3525 can include touch screen sensors, pressure sensors, or fingerprint sensors. In at least one embodiment, wireless transceiver 3526 can be a Wi-Fi transceiver, a Bluetooth transceiver, or a mobile network transceiver such as a 3G, 4G, or Long Term Evolution (LTE) transceiver. In at least one embodiment, firmware interface 3528 enables communication with system firmware, and can be, for example, a unified extensible firmware interface (UEFI). In at least one embodiment, network controller 3534 can enable a network connection to a wired network. In at least one embodiment, a high-performance network controller (not shown) couples with interface bus 3510. In at least one embodiment, audio controller 3546 is a multi-channel high definition audio controller. In at least one embodiment, system 3500 includes an optional legacy I/O controller 3540 for coupling legacy (e.g., Personal System 2 (PS/2)) devices to system 3500. In at least one embodiment, platform controller hub 3530 can also connect to one or more Universal Serial Bus (USB) controllers 3542 connect input devices, such as keyboard and mouse 3543 combinations, a camera 3544, or other USB input devices.

In at least one embodiment, an instance of memory controller 3516 and platform controller hub 3530 may be integrated into a discreet external graphics processor, such as external graphics processor 3512. In at least one embodiment, platform controller hub 3530 and/or memory controller 3516 may be external to one or more processor(s) 3502. For example, in at least one embodiment, system 3500 can include an external memory controller 3516 and platform controller hub 3530, which may be configured as a memory controller hub and peripheral controller hub within a system chipset that is in communication with processor(s) 3502.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment portions or all of inference and/or training logic 1615 may be incorporated into graphics processor 3500. For example, in at least one embodiment, training and/or inferencing techniques described herein may use one or more of ALUs embodied in a 3D pipeline. Moreover, in at least one embodiment, inferencing and/or training operations described herein may be done using logic other than logic illustrated in FIG. 16A or 16B. In at least one embodiment, weight parameters may be stored in on-chip or off-chip memory and/or registers (shown or not shown) that configure ALUs of graphics processor 3500 to perform one or more machine learning algorithms, neural network architectures, use cases, or training techniques described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 36 is a block diagram of a processor 3600 having one or more processor cores 3602A-3602N, an integrated memory controller 3614, and an integrated graphics processor 3608, according to at least one embodiment. In at least one embodiment, processor 3600 can include additional cores up to and including additional core 3602N represented by dashed lined boxes. In at least one embodiment, each of processor cores 3602A-3602N includes one or more internal cache units 3604A-3604N. In at least one embodiment, each processor core also has access to one or more shared cached units 3606.

In at least one embodiment, internal cache units 3604A-3604N and shared cache units 3606 represent a cache memory hierarchy within processor 3600. In at least one embodiment, cache memory units 3604A-3604N may include at least one level of instruction and data cache within each processor core and one or more levels of shared mid-level cache, such as a Level 2 (L2), Level 3 (L3), Level 4 (L4), or other levels of cache, where a highest level of cache before external memory is classified as an LLC. In at least one embodiment, cache coherency logic maintains coherency between various cache units 3606 and 3604A-3604N.

In at least one embodiment, processor 3600 may also include a set of one or more bus controller units 3616 and a system agent core 3610. In at least one embodiment, bus controller units 3616 manage a set of peripheral buses, such as one or more PCI or PCI express busses. In at least one embodiment, system agent core 3610 provides management functionality for various processor components. In at least one embodiment, system agent core 3610 includes one or more integrated memory controllers 3614 to manage access to various external memory devices (not shown).

In at least one embodiment, one or more of processor cores 3602A-3602N include support for simultaneous multi-threading. In at least one embodiment, system agent core 3610 includes components for coordinating and operating cores 3602A-3602N during multi-threaded processing. In at least one embodiment, system agent core 3610 may additionally include a power control unit (PCU), which includes logic and components to regulate one or more power states of processor cores 3602A-3602N and graphics processor 3608.

In at least one embodiment, processor 3600 additionally includes graphics processor 3608 to execute graphics processing operations. In at least one embodiment, graphics processor 3608 couples with shared cache units 3606, and system agent core 3610, including one or more integrated memory controllers 3614. In at least one embodiment, system agent core 3610 also includes a display controller 3611 to drive graphics processor output to one or more coupled displays. In at least one embodiment, display controller 3611 may also be a separate module coupled with graphics processor 3608 via at least one interconnect, or may be integrated within graphics processor 3608.

In at least one embodiment, a ring-based interconnect unit 3612 is used to couple internal components of processor 3600. In at least one embodiment, an alternative interconnect unit may be used, such as a point-to-point interconnect, a switched interconnect, or other techniques. In at least one embodiment, graphics processor 3608 couples with ring interconnect 3612 via an I/O link 3613.

In at least one embodiment, I/O link 3613 represents at least one of multiple varieties of I/O interconnects, including an on package I/O interconnect which facilitates communication between various processor components and a high-performance embedded memory module 3618, such as an eDRAM module. In at least one embodiment, each of processor cores 3602A-3602N and graphics processor 3608 use embedded memory module 3618 as a shared Last Level Cache.

In at least one embodiment, processor cores 3602A-3602N are homogeneous cores executing a common instruction set architecture. In at least one embodiment, processor cores 3602A-3602N are heterogeneous in terms of instruction set architecture (ISA), where one or more of processor cores 3602A-3602N execute a common instruction set, while one or more other cores of processor cores 3602A-3602N executes a subset of a common instruction set or a different instruction set. In at least one embodiment, processor cores 3602A-3602N are heterogeneous in terms of microarchitecture, where one or more cores having a relatively higher power consumption couple with one or more power cores having a lower power consumption. In at least one embodiment, processor 3600 can be implemented on one or more chips or as an SoC integrated circuit.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment portions or all of inference and/or training logic 1615 may be incorporated into graphics processor 3610. For example, in at least one embodiment, training and/or inferencing techniques described herein may use one or more of ALUs embodied in a 3D pipeline, graphics core(s) 3602, shared function logic, or other logic in FIG. 36 . Moreover, in at least one embodiment, inferencing and/or training operations described herein may be done using logic other than logic illustrated in FIG. 16A or 16B. In at least one embodiment, weight parameters may be stored in on-chip or off-chip memory and/or registers (shown or not shown) that configure ALUs of processor 3600 to perform one or more machine learning algorithms, neural network architectures, use cases, or training techniques described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 37 is a block diagram of a graphics processor 3700, which may be a discrete graphics processing unit, or may be a graphics processor integrated with a plurality of processing cores. In at least one embodiment, graphics processor 3700 communicates via a memory mapped I/O interface to registers on graphics processor 3700 and with commands placed into memory. In at least one embodiment, graphics processor 3700 includes a memory interface 3714 to access memory. In at least one embodiment, memory interface 3714 is an interface to local memory, one or more internal caches, one or more shared external caches, and/or to system memory.

In at least one embodiment, graphics processor 3700 also includes a display controller 3702 to drive display output data to a display device 3720. In at least one embodiment, display controller 3702 includes hardware for one or more overlay planes for display device 3720 and composition of multiple layers of video or user interface elements. In at least one embodiment, display device 3720 can be an internal or external display device. In at least one embodiment, display device 3720 is a head mounted display device, such as a virtual reality (VR) display device or an augmented reality (AR) display device. In at least one embodiment, graphics processor 3700 includes a video codec engine 3706 to encode, decode, or transcode media to, from, or between one or more media encoding formats, including, but not limited to Moving Picture Experts Group (MPEG) formats such as MPEG-2, Advanced Video Coding (AVC) formats such as H.264/MPEG-4 AVC, as well as the Society of Motion Picture & Television Engineers (SMPTE) 421M/VC-1, and Joint Photographic Experts Group (JPEG) formats such as JPEG, and Motion JPEG (MJPEG) formats.

In at least one embodiment, graphics processor 3700 includes a block image transfer (BLIT) engine 3704 to perform two-dimensional (2D) rasterizer operations including, for example, bit-boundary block transfers. However, in at least one embodiment, 2D graphics operations are performed using one or more components of a graphics processing engine (GPE) 3710. In at least one embodiment, GPE 3710 is a compute engine for performing graphics operations, including three-dimensional (3D) graphics operations and media operations.

In at least one embodiment, GPE 3710 includes a 3D pipeline 3712 for performing 3D operations, such as rendering three-dimensional images and scenes using processing functions that act upon 3D primitive shapes (e.g., rectangle, triangle, etc.). In at least one embodiment, 3D pipeline 3712 includes programmable and fixed function elements that perform various tasks and/or spawn execution threads to a 3D/Media sub-system 3715. While 3D pipeline 3712 can be used to perform media operations, in at least one embodiment, GPE 3710 also includes a media pipeline 3716 that is used to perform media operations, such as video post-processing and image enhancement.

In at least one embodiment, media pipeline 3716 includes fixed function or programmable logic units to perform one or more specialized media operations, such as video decode acceleration, video de-interlacing, and video encode acceleration in place of, or on behalf of, video codec engine 3706. In at least one embodiment, media pipeline 3716 additionally includes a thread spawning unit to spawn threads for execution on 3D/Media sub-system 3715. In at least one embodiment, spawned threads perform computations for media operations on one or more graphics execution units included in 3D/Media sub-system 3715.

In at least one embodiment, 3D/Media subsystem 3715 includes logic for executing threads spawned by 3D pipeline 3712 and media pipeline 3716. In at least one embodiment, 3D pipeline 3712 and media pipeline 3716 send thread execution requests to 3D/Media subsystem 3715, which includes thread dispatch logic for arbitrating and dispatching various requests to available thread execution resources. In at least one embodiment, execution resources include an array of graphics execution units to process 3D and media threads. In at least one embodiment, 3D/Media subsystem 3715 includes one or more internal caches for thread instructions and data. In at least one embodiment, subsystem 3715 also includes shared memory, including registers and addressable memory, to share data between threads and to store output data.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment portions or all of inference and/or training logic 1615 may be incorporated into graphics processor 3700. For example, in at least one embodiment, training and/or inferencing techniques described herein may use one or more of ALUs embodied in 3D pipeline 3712. Moreover, in at least one embodiment, inferencing and/or training operations described herein may be done using logic other than logic illustrated in FIG. 16A or 16B. In at least one embodiment, weight parameters may be stored in on-chip or off-chip memory and/or registers (shown or not shown) that configure ALUs of graphics processor 3700 to perform one or more machine learning algorithms, neural network architectures, use cases, or training techniques described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 38 is a block diagram of a graphics processing engine 3810 of a graphics processor in accordance with at least one embodiment. In at least one embodiment, graphics processing engine (GPE) 3810 is a version of GPE 3710 shown in FIG. 37 . In at least one embodiment, a media pipeline 3816 is optional and may not be explicitly included within GPE 3810. In at least one embodiment, a separate media and/or image processor is coupled to GPE 3810.

In at least one embodiment, GPE 3810 is coupled to or includes a command streamer 3803, which provides a command stream to a 3D pipeline 3812 and/or media pipeline 3816. In at least one embodiment, command streamer 3803 is coupled to memory, which can be system memory, or one or more of internal cache memory and shared cache memory. In at least one embodiment, command streamer 3803 receives commands from memory and sends commands to 3D pipeline 3812 and/or media pipeline 3816. In at least one embodiment, commands are instructions, primitives, or micro-operations fetched from a ring buffer, which stores commands for 3D pipeline 3812 and media pipeline 3816. In at least one embodiment, a ring buffer can additionally include batch command buffers storing batches of multiple commands. In at least one embodiment, commands for 3D pipeline 3812 can also include references to data stored in memory, such as, but not limited to, vertex and geometry data for 3D pipeline 3812 and/or image data and memory objects for media pipeline 3816. In at least one embodiment, 3D pipeline 3812 and media pipeline 3816 process commands and data by performing operations or by dispatching one or more execution threads to a graphics core array 3814. In at least one embodiment, graphics core array 3814 includes one or more blocks of graphics cores (e.g., graphics core(s) 3815A, graphics core(s) 3815B), each block including one or more graphics cores. In at least one embodiment, each graphics core includes a set of graphics execution resources that includes general-purpose and graphics specific execution logic to perform graphics and compute operations, as well as fixed function texture processing and/or machine learning and artificial intelligence acceleration logic, including inference and/or training logic 1615 in FIG. 16A and FIG. 16B.

In at least one embodiment, 3D pipeline 3812 includes fixed function and programmable logic to process one or more shader programs, such as vertex shaders, geometry shaders, pixel shaders, fragment shaders, compute shaders, or other shader programs, by processing instructions and dispatching execution threads to graphics core array 3814. In at least one embodiment, graphics core array 3814 provides a unified block of execution resources for use in processing shader programs. In at least one embodiment, a multi-purpose execution logic (e.g., execution units) within graphics core(s) 3815A-3815B of graphic core array 3814 includes support for various 3D API shader languages and can execute multiple simultaneous execution threads associated with multiple shaders.

In at least one embodiment, graphics core array 3814 also includes execution logic to perform media functions, such as video and/or image processing. In at least one embodiment, execution units additionally include general-purpose logic that is programmable to perform parallel general-purpose computational operations, in addition to graphics processing operations.

In at least one embodiment, output data generated by threads executing on graphics core array 3814 can output data to memory in a unified return buffer (URB) 3818. In at least one embodiment, URB 3818 can store data for multiple threads. In at least one embodiment, URB 3818 may be used to send data between different threads executing on graphics core array 3814. In at least one embodiment, URB 3818 may additionally be used for synchronization between threads on graphics core array 3814 and fixed function logic within shared function logic 3820.

In at least one embodiment, graphics core array 3814 is scalable, such that graphics core array 3814 includes a variable number of graphics cores, each having a variable number of execution units based on a target power and performance level of GPE 3810. In at least one embodiment, execution resources are dynamically scalable, such that execution resources may be enabled or disabled as needed.

In at least one embodiment, graphics core array 3814 is coupled to shared function logic 3820 that includes multiple resources that are shared between graphics cores in graphics core array 3814. In at least one embodiment, shared functions performed by shared function logic 3820 are embodied in hardware logic units that provide specialized supplemental functionality to graphics core array 3814. In at least one embodiment, shared function logic 3820 includes but is not limited to a sampler unit 3821, a math unit 3822, and inter-thread communication (ITC) logic 3823. In at least one embodiment, one or more cache(s) 3825 are included in, or coupled to, shared function logic 3820.

In at least one embodiment, a shared function is used if demand for a specialized function is insufficient for inclusion within graphics core array 3814. In at least one embodiment, a single instantiation of a specialized function is used in shared function logic 3820 and shared among other execution resources within graphics core array 3814. In at least one embodiment, specific shared functions within shared function logic 3820 that are used extensively by graphics core array 3814 may be included within shared function logic 4116 within graphics core array 3814. In at least one embodiment, shared function logic 4116 within graphics core array 3814 can include some or all logic within shared function logic 3820. In at least one embodiment, all logic elements within shared function logic 3820 may be duplicated within shared function logic 3826 of graphics core array 3814. In at least one embodiment, shared function logic 3820 is excluded in favor of shared function logic 3826 within graphics core array 3814.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment portions or all of inference and/or training logic 1615 may be incorporated into graphics processor 3810. For example, in at least one embodiment, training and/or inferencing techniques described herein may use one or more of ALUs embodied in 3D pipeline 3812, graphics core(s) 3815, shared function logic 3826, shared function logic 3820, or other logic in FIG. 38 . Moreover, in at least one embodiment, inferencing and/or training operations described herein may be done using logic other than logic illustrated in FIG. 16A or 16B. In at least one embodiment, weight parameters may be stored in on-chip or off-chip memory and/or registers (shown or not shown) that configure ALUs of graphics processor 3810 to perform one or more machine learning algorithms, neural network architectures, use cases, or training techniques described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 39 is a block diagram of hardware logic of a graphics processor core 3900, according to at least one embodiment described herein. In at least one embodiment, graphics processor core 3900 is included within a graphics core array. In at least one embodiment, graphics processor core 3900, sometimes referred to as a core slice, can be one or multiple graphics cores within a modular graphics processor. In at least one embodiment, graphics processor core 3900 is exemplary of one graphics core slice, and a graphics processor as described herein may include multiple graphics core slices based on target power and performance envelopes. In at least one embodiment, each graphics core 3900 can include a fixed function block 3930 coupled with multiple sub-cores 3901A-3901F, also referred to as sub-slices, that include modular blocks of general-purpose and fixed function logic.

In at least one embodiment, fixed function block 3930 includes a geometry and fixed function pipeline 3936 that can be shared by all sub-cores in graphics processor 3900, for example, in lower performance and/or lower power graphics processor implementations. In at least one embodiment, geometry and fixed function pipeline 3936 includes a 3D fixed function pipeline, a video front-end unit, a thread spawner and thread dispatcher, and a unified return buffer manager, which manages unified return buffers.

In at least one embodiment, fixed function block 3930 also includes a graphics SoC interface 3937, a graphics microcontroller 3938, and a media pipeline 3939. In at least one embodiment, graphics SoC interface 3937 provides an interface between graphics core 3900 and other processor cores within a system on a chip integrated circuit. In at least one embodiment, graphics microcontroller 3938 is a programmable sub-processor that is configurable to manage various functions of graphics processor 3900, including thread dispatch, scheduling, and preemption. In at least one embodiment, media pipeline 3939 includes logic to facilitate decoding, encoding, pre-processing, and/or post-processing of multimedia data, including image and video data. In at least one embodiment, media pipeline 3939 implements media operations via requests to compute or sampling logic within sub-cores 3901A-3901F.

In at least one embodiment, SoC interface 3937 enables graphics core 3900 to communicate with general-purpose application processor cores (e.g., CPUs) and/or other components within an SoC, including memory hierarchy elements such as a shared last level cache memory, system RAM, and/or embedded on-chip or on-package DRAM. In at least one embodiment, SoC interface 3937 can also enable communication with fixed function devices within an SoC, such as camera imaging pipelines, and enables use of and/or implements global memory atomics that may be shared between graphics core 3900 and CPUs within an SoC. In at least one embodiment, graphics SoC interface 3937 can also implement power management controls for graphics processor core 3900 and enable an interface between a clock domain of graphics processor core 3900 and other clock domains within an SoC. In at least one embodiment, SoC interface 3937 enables receipt of command buffers from a command streamer and global thread dispatcher that are configured to provide commands and instructions to each of one or more graphics cores within a graphics processor. In at least one embodiment, commands and instructions can be dispatched to media pipeline 3939, when media operations are to be performed, or a geometry and fixed function pipeline (e.g., geometry and fixed function pipeline 3936, and/or a geometry and fixed function pipeline 3914) when graphics processing operations are to be performed.

In at least one embodiment, graphics microcontroller 3938 can be configured to perform various scheduling and management tasks for graphics core 3900. In at least one embodiment, graphics microcontroller 3938 can perform graphics and/or compute workload scheduling on various graphics parallel engines within execution unit (EU) arrays 3902A-3902F, 3904A-3904F within sub-cores 3901A-3901F. In at least one embodiment, host software executing on a CPU core of an SoC including graphics core 3900 can submit workloads to one of multiple graphic processor paths, which invokes a scheduling operation on an appropriate graphics engine. In at least one embodiment, scheduling operations include determining which workload to run next, submitting a workload to a command streamer, pre-empting existing workloads running on an engine, monitoring progress of a workload, and notifying host software when a workload is complete. In at least one embodiment, graphics microcontroller 3938 can also facilitate low-power or idle states for graphics core 3900, providing graphics core 3900 with an ability to save and restore registers within graphics core 3900 across low-power state transitions independently from an operating system and/or graphics driver software on a system.

In at least one embodiment, graphics core 3900 may have greater than or fewer than illustrated sub-cores 3901A-3901F, up to N modular sub-cores. For each set of N sub-cores, in at least one embodiment, graphics core 3900 can also include shared function logic 3910, shared and/or cache memory 3912, geometry/fixed function pipeline 3914, as well as additional fixed function logic 3916 to accelerate various graphics and compute processing operations. In at least one embodiment, shared function logic 3910 can include logic units (e.g., sampler, math, and/or inter-thread communication logic) that can be shared by each N sub-cores within graphics core 3900. In at least one embodiment, shared and/or cache memory 3912 can be a last-level cache for N sub-cores 3901A-3901F within graphics core 3900 and can also serve as shared memory that is accessible by multiple sub-cores. In at least one embodiment, geometry/fixed function pipeline 3914 can be included instead of geometry/fixed function pipeline 3936 within fixed function block 3930 and can include similar logic units.

In at least one embodiment, graphics core 3900 includes additional fixed function logic 3916 that can include various fixed function acceleration logic for use by graphics core 3900. In at least one embodiment, additional fixed function logic 3916 includes an additional geometry pipeline for use in position-only shading. In position-only shading, at least two geometry pipelines exist, whereas in a full geometry pipeline within geometry and fixed function pipelines 3914, 3936, and a cull pipeline, which is an additional geometry pipeline that may be included within additional fixed function logic 3916. In at least one embodiment, a cull pipeline is a trimmed down version of a full geometry pipeline. In at least one embodiment, a full pipeline and a cull pipeline can execute different instances of an application, each instance having a separate context. In at least one embodiment, position only shading can hide long cull runs of discarded triangles, enabling shading to be completed earlier in some instances. For example, in at least one embodiment, cull pipeline logic within additional fixed function logic 3916 can execute position shaders in parallel with a main application and generally generates critical results faster than a full pipeline, as a cull pipeline fetches and shades position attributes of vertices, without performing rasterization and rendering of pixels to a frame buffer. In at least one embodiment, a cull pipeline can use generated critical results to compute visibility information for all triangles without regard to whether those triangles are culled. In at least one embodiment, a full pipeline (which in this instance may be referred to as a replay pipeline) can consume visibility information to skip culled triangles to shade only visible triangles that are finally passed to a rasterization phase.

In at least one embodiment, additional fixed function logic 3916 can also include machine-learning acceleration logic, such as fixed function matrix multiplication logic, for implementations including optimizations for machine learning training or inferencing.

In at least one embodiment, within each graphics sub-core 3901A-3901F includes a set of execution resources that may be used to perform graphics, media, and compute operations in response to requests by graphics pipeline, media pipeline, or shader programs. In at least one embodiment, graphics sub-cores 3901A-3901F include multiple EU arrays 3902A-3902F, 3904A-3904F, thread dispatch and inter-thread communication (TD/IC) logic 3903A-3903F, a 3D (e.g., texture) sampler 3905A-3905F, a media sampler 3906A-3906F, a shader processor 3907A-3907F, and shared local memory (SLM) 3908A-3908F. In at least one embodiment, EU arrays 3902A-3902F, 3904A-3904F each include multiple execution units, which are general-purpose graphics processing units capable of performing floating-point and integer/fixed-point logic operations in service of a graphics, media, or compute operation, including graphics, media, or compute shader programs. In at least one embodiment, TD/IC logic 3903A-3903F performs local thread dispatch and thread control operations for execution units within a sub-core and facilitates communication between threads executing on execution units of a sub-core. In at least one embodiment, 3D samplers 3905A-3905F can read texture or other 3D graphics related data into memory. In at least one embodiment, 3D samplers can read texture data differently based on a configured sample state and texture format associated with a given texture. In at least one embodiment, media samplers 3906A-3906F can perform similar read operations based on a type and format associated with media data. In at least one embodiment, each graphics sub-core 3901A-3901F can alternately include a unified 3D and media sampler. In at least one embodiment, threads executing on execution units within each of sub-cores 3901A-3901F can make use of shared local memory 3908A-3908F within each sub-core, to enable threads executing within a thread group to execute using a common pool of on-chip memory.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, portions or all of inference and/or training logic 1615 may be incorporated into graphics processor 3910. For example, in at least one embodiment, training and/or inferencing techniques described herein may use one or more of ALUs embodied in a 3D pipeline, graphics microcontroller 3938, geometry and fixed function pipeline 3914 and 3936, or other logic in FIG. 39 . Moreover, in at least one embodiment, inferencing and/or training operations described herein may be done using logic other than logic illustrated in FIG. 16A or 16B. In at least one embodiment, weight parameters may be stored in on-chip or off-chip memory and/or registers (shown or not shown) that configure ALUs of graphics processor 3900 to perform one or more machine learning algorithms, neural network architectures, use cases, or training techniques described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIGS. 40A-40B illustrate thread execution logic 4000 including an array of processing elements of a graphics processor core according to at least one embodiment. FIG. 40A illustrates at least one embodiment, in which thread execution logic 4000 is used. FIG. 40B illustrates exemplary internal details of a graphics execution unit 4008, according to at least one embodiment.

As illustrated in FIG. 40A, in at least one embodiment, thread execution logic 4000 includes a shader processor 4002, a thread dispatcher 4004, an instruction cache 4006, a scalable execution unit array including a plurality of execution units 4007A-4007N and 4008A-4008N, a sampler 4010, a data cache 4012, and a data port 4014. In at least one embodiment, a scalable execution unit array can dynamically scale by enabling or disabling one or more execution units (e.g., any of execution unit 4008A-N or 4007A-N) based on computational requirements of a workload, for example. In at least one embodiment, scalable execution units are interconnected via an interconnect fabric that links to each execution unit. In at least one embodiment, thread execution logic 4000 includes one or more connections to memory, such as system memory or cache memory, through one or more of instruction cache 4006, data port 4014, sampler 4010, and execution units 4007 or 4008. In at least one embodiment, each execution unit (e.g., 4007A) is a stand-alone programmable general-purpose computational unit that is capable of executing multiple simultaneous hardware threads while processing multiple data elements in parallel for each thread. In at least one embodiment, array of execution units 4007 and/or 4008 is scalable to include any number individual execution units.

In at least one embodiment, execution units 4007 and/or 4008 are primarily used to execute shader programs. In at least one embodiment, shader processor 4002 can process various shader programs and dispatch execution threads associated with shader programs via a thread dispatcher 4004. In at least one embodiment, thread dispatcher 4004 includes logic to arbitrate thread initiation requests from graphics and media pipelines and instantiate requested threads on one or more execution units in execution units 4007 and/or 4008. For example, in at least one embodiment, a geometry pipeline can dispatch vertex, tessellation, or geometry shaders to thread execution logic for processing. In at least one embodiment, thread dispatcher 4004 can also process runtime thread spawning requests from executing shader programs.

In at least one embodiment, execution units 4007 and/or 4008 support an instruction set that includes native support for many standard 3D graphics shader instructions, such that shader programs from graphics libraries (e.g., Direct 3D and OpenGL) are executed with a minimal translation. In at least one embodiment, execution units support vertex and geometry processing (e.g., vertex programs, geometry programs, and/or vertex shaders), pixel processing (e.g., pixel shaders, fragment shaders) and general-purpose processing (e.g., compute and media shaders). In at least one embodiment, each of execution units 4007 and/or 4008, which include one or more arithmetic logic units (ALUs), is capable of multi-issue single instruction multiple data (SIMD) execution and multi-threaded operation enables an efficient execution environment despite higher latency memory accesses. In at least one embodiment, each hardware thread within each execution unit has a dedicated high-bandwidth register file and associated independent thread-state. In at least one embodiment, execution is multi-issue per clock to pipelines capable of integer, single and double precision floating point operations, SIMD branch capability, logical operations, transcendental operations, and other miscellaneous operations. In at least one embodiment, while waiting for data from memory or one of shared functions, dependency logic within execution units 4007 and/or 4008 causes a waiting thread to sleep until requested data has been returned. In at least one embodiment, while an awaiting thread is sleeping, hardware resources may be devoted to processing other threads. For example, in at least one embodiment, during a delay associated with a vertex shader operation, an execution unit can perform operations for a pixel shader, fragment shader, or another type of shader program, including a different vertex shader.

In at least one embodiment, each execution unit in execution units 4007 and/or 4008 operates on arrays of data elements. In at least one embodiment, a number of data elements is an “execution size,” or number of channels for an instruction. In at least one embodiment, an execution channel is a logical unit of execution for data element access, masking, and flow control within instructions. In at least one embodiment, a number of channels may be independent of a number of physical arithmetic logic units (ALUs) or floating point units (FPUs) for a particular graphics processor. In at least one embodiment, execution units 4007 and/or 4008 support integer and floating-point data types.

In at least one embodiment, an execution unit instruction set includes SIMD instructions. In at least one embodiment, various data elements can be stored as a packed data type in a register and execution unit will process various elements based on data size of elements. For example, in at least one embodiment, when operating on a 256-bit wide vector, 256 bits of a vector are stored in a register and an execution unit operates on a vector as four separate 64-bit packed data elements (Quad-Word (QW) size data elements), eight separate 32-bit packed data elements (Double Word (DW) size data elements), sixteen separate 16-bit packed data elements (Word (W) size data elements), or thirty-two separate 8-bit data elements (byte (B) size data elements). However, in at least one embodiment, different vector widths and register sizes are possible.

In at least one embodiment, one or more execution units can be combined into a fused execution unit 4009A-4009N having thread control logic (4011A-4011N) that is common to fused EUs such as execution unit 4007A fused with execution unit 4008A into fused execution unit 4009A. In at least one embodiment, multiple EUs can be fused into an EU group. In at least one embodiment, each EU in a fused EU group can be configured to execute a separate SIMD hardware thread, with a number of EUs in a fused EU group possibly varying according to various embodiments. In at least one embodiment, various SIMD widths can be performed per-EU, including but not limited to SIMD8, SIMD16, and SIMD32. In at least one embodiment, each fused graphics execution unit 4009A-4009N includes at least two execution units. For example, in at least one embodiment, fused execution unit 4009A includes a first EU 4007A, second EU 4008A, and thread control logic 4011A that is common to first EU 4007A and second EU 4008A. In at least one embodiment, thread control logic 4011A controls threads executed on fused graphics execution unit 4009A, allowing each EU within fused execution units 4009A-4009N to execute using a common instruction pointer register.

In at least one embodiment, one or more internal instruction caches (e.g., 4006) are included in thread execution logic 4000 to cache thread instructions for execution units. In at least one embodiment, one or more data caches (e.g., 4012) are included to cache thread data during thread execution. In at least one embodiment, sampler 4010 is included to provide texture sampling for 3D operations and media sampling for media operations. In at least one embodiment, sampler 4010 includes specialized texture or media sampling functionality to process texture or media data during sampling process before providing sampled data to an execution unit.

During execution, in at least one embodiment, graphics and media pipelines send thread initiation requests to thread execution logic 4000 via thread spawning and dispatch logic. In at least one embodiment, once a group of geometric objects has been processed and rasterized into pixel data, pixel processor logic (e.g., pixel shader logic, fragment shader logic, etc.) within shader processor 4002 is invoked to further compute output information and cause results to be written to output surfaces (e.g., color buffers, depth buffers, stencil buffers, etc.). In at least one embodiment, a pixel shader or a fragment shader calculates values of various vertex attributes that are to be interpolated across a rasterized object. In at least one embodiment, pixel processor logic within shader processor 4002 then executes an application programming interface (API)-supplied pixel or fragment shader program. In at least one embodiment, to execute a shader program, shader processor 4002 dispatches threads to an execution unit (e.g., 4008A) via thread dispatcher 4004. In at least one embodiment, shader processor 4002 uses texture sampling logic in sampler 4010 to access texture data in texture maps stored in memory. In at least one embodiment, arithmetic operations on texture data and input geometry data compute pixel color data for each geometric fragment, or discards one or more pixels from further processing.

In at least one embodiment, data port 4014 provides a memory access mechanism for thread execution logic 4000 to output processed data to memory for further processing on a graphics processor output pipeline. In at least one embodiment, data port 4014 includes or couples to one or more cache memories (e.g., data cache 4012) to cache data for memory access via a data port.

As illustrated in FIG. 40B, in at least one embodiment, a graphics execution unit 4008 can include an instruction fetch unit 4037, a general register file array (GRF) 4024, an architectural register file array (ARF) 4026, a thread arbiter 4022, a send unit 4030, a branch unit 4032, a set of SIMD floating point units (FPUs) 4034, and a set of dedicated integer SIMD ALUs 4035. In at least one embodiment, GRF 4024 and ARF 4026 includes a set of general register files and architecture register files associated with each simultaneous hardware thread that may be active in graphics execution unit 4008. In at least one embodiment, per thread architectural state is maintained in ARF 4026, while data used during thread execution is stored in GRF 4024. In at least one embodiment, execution state of each thread, including instruction pointers for each thread, can be held in thread-specific registers in ARF 4026.

In at least one embodiment, graphics execution unit 4008 has an architecture that is a combination of Simultaneous Multi-Threading (SMT) and fine-grained Interleaved Multi-Threading (IMT). In at least one embodiment, architecture has a modular configuration that can be fine-tuned at design time based on a target number of simultaneous threads and number of registers per execution unit, where execution unit resources are divided across logic used to execute multiple simultaneous threads.

In at least one embodiment, graphics execution unit 4008 can co-issue multiple instructions, which may each be different instructions. In at least one embodiment, thread arbiter 4022 of graphics execution unit thread 4008 can dispatch instructions to one of send unit 4030, branch unit 4032, or SIMD FPU(s) 4034 for execution. In at least one embodiment, each execution thread can access 128 general-purpose registers within GRF 4024, where each register can store 32 bytes, accessible as a SIMD 8-element vector of 32-bit data elements. In at least one embodiment, each execution unit thread has access to 4 kilobytes within GRF 4024, although embodiments are not so limited, and greater or fewer register resources may be provided in other embodiments. In at least one embodiment, up to seven threads can execute simultaneously, although a number of threads per execution unit can also vary according to embodiments. In at least one embodiment, in which seven threads may access 4 kilobytes, GRF 4024 can store a total of 28 kilobytes. In at least one embodiment, flexible addressing modes can permit registers to be addressed together to build effectively wider registers or to represent strided rectangular block data structures.

In at least one embodiment, memory operations, sampler operations, and other longer-latency system communications are dispatched via “send” instructions that are executed by message passing to send unit 4030. In at least one embodiment, branch instructions are dispatched to branch unit 4032 to facilitate SIMD divergence and eventual convergence.

In at least one embodiment, graphics execution unit 4008 includes one or more SIMD floating point units (FPU(s)) 4034 to perform floating-point operations. In at least one embodiment, FPU(s) 4034 also support integer computation. In at least one embodiment, FPU(s) 4034 can SIMD execute up to M number of 32-bit floating-point (or integer) operations, or SIMD execute up to 2M 16-bit integer or 16-bit floating-point operations. In at least one embodiment, at least one FPU provides extended math capability to support high-throughput transcendental math functions and double precision 64-bit floating-point. In at least one embodiment, a set of 8-bit integer SIMD ALUs 4035 are also present, and may be specifically optimized to perform operations associated with machine learning computations.

In at least one embodiment, arrays of multiple instances of graphics execution unit 4008 can be instantiated in a graphics sub-core grouping (e.g., a sub-slice). In at least one embodiment, execution unit 4008 can execute instructions across a plurality of execution channels. In at least one embodiment, each thread executed on graphics execution unit 4008 is executed on a different channel.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, portions or all of inference and/or training logic 1615 may be incorporated into thread execution logic 4000. Moreover, in at least one embodiment, inferencing and/or training operations described herein may be done using logic other than logic illustrated in FIG. 16A or 16B. In at least one embodiment, weight parameters may be stored in on-chip or off-chip memory and/or registers (shown or not shown) that configure ALUs thread of execution logic 4000 to perform one or more machine learning algorithms, neural network architectures, use cases, or training techniques described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 41 illustrates a parallel processing unit (“PPU”) 4100, according to at least one embodiment. In at least one embodiment, PPU 4100 is configured with machine-readable code that, if executed by PPU 4100, causes PPU 4100 to perform some or all of processes and techniques described throughout this disclosure. In at least one embodiment, PPU 4100 is a multi-threaded processor that is implemented on one or more integrated circuit devices and that utilizes multithreading as a latency-hiding technique designed to process computer-readable instructions (also referred to as machine-readable instructions or simply instructions) on multiple threads in parallel. In at least one embodiment, a thread refers to a thread of execution and is an instantiation of a set of instructions configured to be executed by PPU 4100. In at least one embodiment, PPU 4100 is a graphics processing unit (“GPU”) configured to implement a graphics rendering pipeline for processing three-dimensional (“3D”) graphics data in order to generate two-dimensional (“2D”) image data for display on a display device such as a liquid crystal display (“LCD”) device. In at least one embodiment, PPU 4100 is utilized to perform computations such as linear algebra operations and machine-learning operations. FIG. 41 illustrates an example parallel processor for illustrative purposes only and should be construed as a non-limiting example of processor architectures contemplated within scope of this disclosure and that any suitable processor may be employed to supplement and/or substitute for same.

In at least one embodiment, one or more PPUs 4100 are configured to accelerate High Performance Computing (“HPC”), data center, and machine learning applications. In at least one embodiment, PPU 4100 is configured to accelerate deep learning systems and applications including following non-limiting examples: autonomous vehicle platforms, deep learning, high-accuracy speech, image, text recognition systems, intelligent video analytics, molecular simulations, drug discovery, disease diagnosis, weather forecasting, big data analytics, astronomy, molecular dynamics simulation, financial modeling, robotics, factory automation, real-time language translation, online search optimizations, and personalized user recommendations, and more.

In at least one embodiment, PPU 4100 includes, without limitation, an Input/Output (“I/O”) unit 4106, a front-end unit 4110, a scheduler unit 4112, a work distribution unit 4114, a hub 4116, a crossbar (“XBar”) 4120, one or more general processing clusters (“GPCs”) 4118, and one or more partition units (“memory partition units”) 4122. In at least one embodiment, PPU 4100 is connected to a host processor or other PPUs 4100 via one or more high-speed GPU interconnects (“GPU interconnects”) 4108. In at least one embodiment, PPU 4100 is connected to a host processor or other peripheral devices via a system bus 4102. In at least one embodiment, PPU 4100 is connected to a local memory comprising one or more memory devices (“memory”) 4104. In at least one embodiment, memory devices 4104 include, without limitation, one or more dynamic random access memory (“DRAM”) devices. In at least one embodiment, one or more DRAM devices are configured and/or configurable as high-bandwidth memory (“HBM”) subsystems, with multiple DRAM dies stacked within each device.

In at least one embodiment, high-speed GPU interconnect 4108 may refer to a wire-based multi-lane communications link that is used by systems to scale and include one or more PPUs 4100 combined with one or more central processing units (“CPUs”), supports cache coherence between PPUs 4100 and CPUs, and CPU mastering. In at least one embodiment, data and/or commands are transmitted by high-speed GPU interconnect 4108 through hub 4116 to/from other units of PPU 4100 such as one or more copy engines, video encoders, video decoders, power management units, and other components which may not be explicitly illustrated in FIG. 41 .

In at least one embodiment, I/O unit 4106 is configured to transmit and receive communications (e.g., commands, data) from a host processor (not illustrated in FIG. 41 ) over system bus 4102. In at least one embodiment, I/O unit 4106 communicates with host processor directly via system bus 4102 or through one or more intermediate devices such as a memory bridge. In at least one embodiment, I/O unit 4106 may communicate with one or more other processors, such as one or more of PPUs 4100 via system bus 4102. In at least one embodiment, I/O unit 4106 implements a Peripheral Component Interconnect Express (“PCIe”) interface for communications over a PCIe bus. In at least one embodiment, I/O unit 4106 implements interfaces for communicating with external devices.

In at least one embodiment, I/O unit 4106 decodes packets received via system bus 4102. In at least one embodiment, at least some packets represent commands configured to cause PPU 4100 to perform various operations. In at least one embodiment, I/O unit 4106 transmits decoded commands to various other units of PPU 4100 as specified by commands. In at least one embodiment, commands are transmitted to front-end unit 4110 and/or transmitted to hub 4116 or other units of PPU 4100 such as one or more copy engines, a video encoder, a video decoder, a power management unit, etc. (not explicitly illustrated in FIG. 41 ). In at least one embodiment, I/O unit 4106 is configured to route communications between and among various logical units of PPU 4100.

In at least one embodiment, a program executed by host processor encodes a command stream in a buffer that provides workloads to PPU 4100 for processing. In at least one embodiment, a workload comprises instructions and data to be processed by those instructions. In at least one embodiment, a buffer is a region in a memory that is accessible (e.g., read/write) by both a host processor and PPU 4100—a host interface unit may be configured to access that buffer in a system memory connected to system bus 4102 via memory requests transmitted over system bus 4102 by I/O unit 4106. In at least one embodiment, a host processor writes a command stream to a buffer and then transmits a pointer to a start of a command stream to PPU 4100 such that front-end unit 4110 receives pointers to one or more command streams and manages one or more command streams, reading commands from command streams and forwarding commands to various units of PPU 4100.

In at least one embodiment, front-end unit 4110 is coupled to scheduler unit 4112 that configures various GPCs 4118 to process tasks defined by one or more command streams. In at least one embodiment, scheduler unit 4112 is configured to track state information related to various tasks managed by scheduler unit 4112 where state information may indicate which of GPCs 4118 a task is assigned to, whether task is active or inactive, a priority level associated with task, and so forth. In at least one embodiment, scheduler unit 4112 manages execution of a plurality of tasks on one or more of GPCs 4118.

In at least one embodiment, scheduler unit 4112 is coupled to work distribution unit 4114 that is configured to dispatch tasks for execution on GPCs 4118. In at least one embodiment, work distribution unit 4114 tracks a number of scheduled tasks received from scheduler unit 4112 and work distribution unit 4114 manages a pending task pool and an active task pool for each of GPCs 4118. In at least one embodiment, pending task pool comprises a number of slots (e.g., 32 slots) that contain tasks assigned to be processed by a particular GPC 4118; an active task pool may comprise a number of slots (e.g., 4 slots) for tasks that are actively being processed by GPCs 4118 such that as one of GPCs 4118 completes execution of a task, that task is evicted from that active task pool for GPC 4118 and another task from a pending task pool is selected and scheduled for execution on GPC 4118. In at least one embodiment, if an active task is idle on GPC 4118, such as while waiting for a data dependency to be resolved, then that active task is evicted from GPC 4118 and returned to that pending task pool while another task in that pending task pool is selected and scheduled for execution on GPC 4118.

In at least one embodiment, work distribution unit 4114 communicates with one or more GPCs 4118 via XBar 4120. In at least one embodiment, XBar 4120 is an interconnect network that couples many of units of PPU 4100 to other units of PPU 4100 and can be configured to couple work distribution unit 4114 to a particular GPC 4118. In at least one embodiment, one or more other units of PPU 4100 may also be connected to XBar 4120 via hub 4116.

In at least one embodiment, tasks are managed by scheduler unit 4112 and dispatched to one of GPCs 4118 by work distribution unit 4114. In at least one embodiment, GPC 4118 is configured to process task and generate results. In at least one embodiment, results may be consumed by other tasks within GPC 4118, routed to a different GPC 4118 via XBar 4120, or stored in memory 4104. In at least one embodiment, results can be written to memory 4104 via partition units 4122, which implement a memory interface for reading and writing data to/from memory 4104. In at least one embodiment, results can be transmitted to another PPU 4104 or CPU via high-speed GPU interconnect 4108. In at least one embodiment, PPU 4100 includes, without limitation, a number U of partition units 4122 that is equal to a number of separate and distinct memory devices 4104 coupled to PPU 4100, as described in more detail herein in conjunction with FIG. 43 .

In at least one embodiment, a host processor executes a driver kernel that implements an application programming interface (“API”) that enables one or more applications executing on a host processor to schedule operations for execution on PPU 4100. In at least one embodiment, multiple compute applications are simultaneously executed by PPU 4100 and PPU 4100 provides isolation, quality of service (“QoS”), and independent address spaces for multiple compute applications. In at least one embodiment, an application generates instructions (e.g., in form of API calls) that cause a driver kernel to generate one or more tasks for execution by PPU 4100 and that driver kernel outputs tasks to one or more streams being processed by PPU 4100. In at least one embodiment, each task comprises one or more groups of related threads, which may be referred to as a warp. In at least one embodiment, a warp comprises a plurality of related threads (e.g., 32 threads) that can be executed in parallel. In at least one embodiment, cooperating threads can refer to a plurality of threads including instructions to perform task and that exchange data through shared memory. In at least one embodiment, threads and cooperating threads are described in more detail in conjunction with FIG. 43 .

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, deep learning application processor is used to train a machine learning model, such as a neural network, to predict or infer information provided to PPU 4100. In at least one embodiment, deep learning application processor 4100 is used to infer or predict information based on a trained machine learning model (e.g., neural network) that has been trained by another processor or system or by PPU 4100. In at least one embodiment, PPU 4100 may be used to perform one or more neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 42 illustrates a general processing cluster (“GPC”) 4200, according to at least one embodiment. In at least one embodiment, GPC 4200 is GPC 4118 of FIG. 41 . In at least one embodiment, each GPC 4200 includes, without limitation, a number of hardware units for processing tasks and each GPC 4200 includes, without limitation, a pipeline manager 4202, a pre-raster operations unit (“preROP”) 4204, a raster engine 4208, a work distribution crossbar (“WDX”) 4216, a memory management unit (“MMU”) 4218, one or more Data Processing Clusters (“DPCs”) 4206, and any suitable combination of parts.

In at least one embodiment, operation of GPC 4200 is controlled by pipeline manager 4202. In at least one embodiment, pipeline manager 4202 manages configuration of one or more DPCs 4206 for processing tasks allocated to GPC 4200. In at least one embodiment, pipeline manager 4202 configures at least one of one or more DPCs 4206 to implement at least a portion of a graphics rendering pipeline. In at least one embodiment, DPC 4206 is configured to execute a vertex shader program on a programmable streaming multi-processor (“SM”) 4214. In at least one embodiment, pipeline manager 4202 is configured to route packets received from a work distribution unit to appropriate logical units within GPC 4200, in at least one embodiment, and some packets may be routed to fixed function hardware units in preROP 4204 and/or raster engine 4208 while other packets may be routed to DPCs 4206 for processing by a primitive engine 4212 or SM 4214. In at least one embodiment, pipeline manager 4202 configures at least one of DPCs 4206 to implement a neural network model and/or a computing pipeline.

In at least one embodiment, preROP unit 4204 is configured, in at least one embodiment, to route data generated by raster engine 4208 and DPCs 4206 to a Raster Operations (“ROP”) unit in partition unit 4122, described in more detail above in conjunction with FIG. 41 . In at least one embodiment, preROP unit 4204 is configured to perform optimizations for color blending, organize pixel data, perform address translations, and more. In at least one embodiment, raster engine 4208 includes, without limitation, a number of fixed function hardware units configured to perform various raster operations, in at least one embodiment, and raster engine 4208 includes, without limitation, a setup engine, a coarse raster engine, a culling engine, a clipping engine, a fine raster engine, a tile coalescing engine, and any suitable combination thereof. In at least one embodiment, setup engine receives transformed vertices and generates plane equations associated with geometric primitive defined by vertices; plane equations are transmitted to a coarse raster engine to generate coverage information (e.g., an x, y coverage mask for a tile) for primitive; output of a coarse raster engine is transmitted to a culling engine where fragments associated with a primitive that fail a z-test are culled, and transmitted to a clipping engine where fragments lying outside a viewing frustum are clipped. In at least one embodiment, fragments that survive clipping and culling are passed to a fine raster engine to generate attributes for pixel fragments based on plane equations generated by a setup engine. In at least one embodiment, an output of raster engine 4208 comprises fragments to be processed by any suitable entity, such as by a fragment shader implemented within DPC 4206.

In at least one embodiment, each DPC 4206 included in GPC 4200 comprises, without limitation, an M-Pipe Controller (“MPC”) 4210; primitive engine 4212; one or more SMs 4214; and any suitable combination thereof. In at least one embodiment, MPC 4210 controls operation of DPC 4206, routing packets received from pipeline manager 4202 to appropriate units in DPC 4206. In at least one embodiment, packets associated with a vertex are routed to primitive engine 4212, which is configured to fetch vertex attributes associated with a vertex from memory; in contrast, packets associated with a shader program may be transmitted to SM 4214.

In at least one embodiment, SM 4214 comprises, without limitation, a programmable streaming processor that is configured to process tasks represented by a number of threads. In at least one embodiment, SM 4214 is multi-threaded and configured to execute a plurality of threads (e.g., 32 threads) from a particular group of threads concurrently and implements a Single-Instruction, Multiple-Data (“SIMD”) architecture where each thread in a group of threads (e.g., a warp) is configured to process a different set of data based on same set of instructions. In at least one embodiment, all threads in group of threads execute a common set of instructions. In at least one embodiment, SM 4214 implements a Single-Instruction, Multiple Thread (“SIMT”) architecture wherein each thread in a group of threads is configured to process a different set of data based on that common set of instructions, but where individual threads in a group of threads are allowed to diverge during execution. In at least one embodiment, a program counter, call stack, and execution state is maintained for each warp, enabling concurrency between warps and serial execution within warps when threads within a warp diverge. In another embodiment, a program counter, call stack, and execution state is maintained for each individual thread, enabling equal concurrency between all threads, within and between warps. In at least one embodiment, execution state is maintained for each individual thread and threads executing common instructions may be converged and executed in parallel for better efficiency. At least one embodiment of SM 4214 is described in more detail herein.

In at least one embodiment, MMU 4218 provides an interface between GPC 4200 and a memory partition unit (e.g., partition unit 4122 of FIG. 41 ) and MMU 4218 provides translation of virtual addresses into physical addresses, memory protection, and arbitration of memory requests. In at least one embodiment, MMU 4218 provides one or more translation lookaside buffers (“TLBs”) for performing translation of virtual addresses into physical addresses in memory.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, deep learning application processor is used to train a machine learning model, such as a neural network, to predict or infer information provided to GPC 4200. In at least one embodiment, GPC 4200 is used to infer or predict information based on a trained machine learning model (e.g., neural network) that has been trained by another processor or system or by GPC 4200. In at least one embodiment, GPC 4200 may be used to perform one or more neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 43 illustrates a memory partition unit 4300 of a parallel processing unit (“PPU”), in accordance with at least one embodiment. In at least one embodiment, memory partition unit 4300 includes, without limitation, a Raster Operations (“ROP”) unit 4302, a level two (“L2”) cache 4304, a memory interface 4306, and any suitable combination thereof. In at least one embodiment, memory interface 4306 is coupled to memory. In at least one embodiment, memory interface 4306 may implement 32, 64, 128, 1024-bit data buses, or like, for high-speed data transfer. In at least one embodiment, PPU incorporates U memory interfaces 4306 where U is a positive integer, with one memory interface 4306 per pair of partition units 4300, where each pair of partition units 4300 is connected to a corresponding memory device. For example, in at least one embodiment, PPU may be connected to up to Y memory devices, such as high bandwidth memory stacks or graphics double-data-rate, version 5, synchronous dynamic random access memory (“GDDR5 SDRAM”).

In at least one embodiment, memory interface 4306 implements a high bandwidth memory second generation (“HBM2”) memory interface and Y equals half of U. In at least one embodiment, HBM2 memory stacks are located on a physical package with a PPU, providing substantial power and area savings compared with conventional GDDR5 SDRAM systems. In at least one embodiment, each HBM2 stack includes, without limitation, four memory dies with Y=4, with each HBM2 stack including two 128-bit channels per die for a total of 8 channels and a data bus width of 1024 bits. In at least one embodiment, that memory supports Single-Error Correcting Double-Error Detecting (“SECDED”) Error Correction Code (“ECC”) to protect data. In at least one embodiment, ECC can provide higher reliability for compute applications that are sensitive to data corruption.

In at least one embodiment, PPU implements a multi-level memory hierarchy. In at least one embodiment, memory partition unit 4300 supports a unified memory to provide a single unified virtual address space for central processing unit (“CPU”) and PPU memory, enabling data sharing between virtual memory systems. In at least one embodiment frequency of accesses by a PPU to a memory located on other processors is traced to ensure that memory pages are moved to physical memory of PPU that is accessing pages more frequently. In at least one embodiment, high-speed GPU interconnect 4108 supports address translation services allowing PPU to directly access a CPU's page tables and providing full access to CPU memory by a PPU.

In at least one embodiment, copy engines transfer data between multiple PPUs or between PPUs and CPUs. In at least one embodiment, copy engines can generate page faults for addresses that are not mapped into page tables and memory partition unit 4300 then services page faults, mapping addresses into page table, after which copy engine performs a transfer. In at least one embodiment, memory is pinned (i.e., non-pageable) for multiple copy engine operations between multiple processors, substantially reducing available memory. In at least one embodiment, with hardware page faulting, addresses can be passed to copy engines without regard as to whether memory pages are resident, and a copy process is transparent.

Data from memory 4104 of FIG. 41 or other system memory is fetched by memory partition unit 4300 and stored in L2 cache 4304, which is located on-chip and is shared between various GPCs, in accordance with at least one embodiment. Each memory partition unit 4300, in at least one embodiment, includes, without limitation, at least a portion of L2 cache associated with a corresponding memory device. In at least one embodiment, lower level caches are implemented in various units within GPCs. In at least one embodiment, each of SMs 4214 in FIG. 42 may implement a Level 1 (“L1”) cache wherein that L1 cache is private memory that is dedicated to a particular SM 4214 and data from L2 cache 4304 is fetched and stored in each L1 cache for processing in functional units of SMs 4214. In at least one embodiment, L2 cache 4304 is coupled to memory interface 4306 and XBar 4120 shown in FIG. 41 .

ROP unit 4302 performs graphics raster operations related to pixel color, such as color compression, pixel blending, and more, in at least one embodiment. ROP unit 4302, in at least one embodiment, implements depth testing in conjunction with raster engine 4208, receiving a depth for a sample location associated with a pixel fragment from a culling engine of raster engine 4208. In at least one embodiment, depth is tested against a corresponding depth in a depth buffer for a sample location associated with a fragment. In at least one embodiment, if that fragment passes that depth test for that sample location, then ROP unit 4302 updates depth buffer and transmits a result of that depth test to raster engine 4208. It will be appreciated that a number of partition units 4300 may be different than a number of GPCs and, therefore, each ROP unit 4302 can, in at least one embodiment, be coupled to each GPC. In at least one embodiment, ROP unit 4302 tracks packets received from different GPCs and determines whether a result generated by ROP unit 4302 is to be routed to through XBar 4120.

FIG. 44 illustrates a streaming multi-processor (“SM”) 4400, according to at least one embodiment. In at least one embodiment, SM 4400 is SM of FIG. 42 . In at least one embodiment, SM 4400 includes, without limitation, an instruction cache 4402, one or more scheduler units 4404, a register file 4408, one or more processing cores (“cores”) 4410, one or more special function units (“SFUs”) 4412, one or more load/store units (“LSUs”) 4414, an interconnect network 4416, a shared memory/level one (“L1”) cache 4418, and/or any suitable combination thereof.

In at least one embodiment, a work distribution unit dispatches tasks for execution on general processing clusters (“GPCs”) of parallel processing units (“PPUs”) and each task is allocated to a particular Data Processing Cluster (“DPC”) within a GPC and, if a task is associated with a shader program, that task is allocated to one of SMs 4400. In at least one embodiment, scheduler unit 4404 receives tasks from a work distribution unit and manages instruction scheduling for one or more thread blocks assigned to SM 4400. In at least one embodiment, scheduler unit 4404 schedules thread blocks for execution as warps of parallel threads, wherein each thread block is allocated at least one warp. In at least one embodiment, each warp executes threads. In at least one embodiment, scheduler unit 4404 manages a plurality of different thread blocks, allocating warps to different thread blocks and then dispatching instructions from plurality of different cooperative groups to various functional units (e.g., processing cores 4410, SFUs 4412, and LSUs 4414) during each clock cycle.

In at least one embodiment, Cooperative Groups may refer to a programming model for organizing groups of communicating threads that allows developers to express granularity at which threads are communicating, enabling expression of richer, more efficient parallel decompositions. In at least one embodiment, cooperative launch APIs support synchronization amongst thread blocks for execution of parallel algorithms. In at least one embodiment, applications of conventional programming models provide a single, simple construct for synchronizing cooperating threads: a barrier across all threads of a thread block (e.g., syncthreads( ) function). However, in at least one embodiment, programmers may define groups of threads at smaller than thread block granularities and synchronize within defined groups to enable greater performance, design flexibility, and software reuse in form of collective group-wide function interfaces. In at least one embodiment, Cooperative Groups enables programmers to define groups of threads explicitly at sub-block (i.e., as small as a single thread) and multi-block granularities, and to perform collective operations such as synchronization on threads in a cooperative group. In at least one embodiment, that programming model supports clean composition across software boundaries, so that libraries and utility functions can synchronize safely within their local context without having to make assumptions about convergence. In at least one embodiment, Cooperative Groups primitives enable new patterns of cooperative parallelism, including, without limitation, producer-consumer parallelism, opportunistic parallelism, and global synchronization across an entire grid of thread blocks.

In at least one embodiment, a dispatch unit 4406 is configured to transmit instructions to one or more functional units and scheduler unit 4404 and includes, without limitation, two dispatch units 4406 that enable two different instructions from a common warp to be dispatched during each clock cycle. In at least one embodiment, each scheduler unit 4404 includes a single dispatch unit 4406 or additional dispatch units 4406.

In at least one embodiment, each SM 4400, in at least one embodiment, includes, without limitation, register file 4408 that provides a set of registers for functional units of SM 4400. In at least one embodiment, register file 4408 is divided between each functional unit such that each functional unit is allocated a dedicated portion of register file 4408. In at least one embodiment, register file 4408 is divided between different warps being executed by SM 4400 and register file 4408 provides temporary storage for operands connected to data paths of functional units. In at least one embodiment, each SM 4400 comprises, without limitation, a plurality of L processing cores 4410, where L is a positive integer. In at least one embodiment, SM 4400 includes, without limitation, a large number (e.g., 128 or more) of distinct processing cores 4410. In at least one embodiment, each processing core 4410 includes, without limitation, a fully-pipelined, single-precision, double-precision, and/or mixed precision processing unit that includes, without limitation, a floating point arithmetic logic unit and an integer arithmetic logic unit. In at least one embodiment, floating point arithmetic logic units implement IEEE 754-2008 standard for floating point arithmetic. In at least one embodiment, processing cores 4410 include, without limitation, 64 single-precision (32-bit) floating point cores, 64 integer cores, 32 double-precision (64-bit) floating point cores, and 8 tensor cores.

Tensor cores are configured to perform matrix operations in accordance with at least one embodiment. In at least one embodiment, one or more tensor cores are included in processing cores 4410. In at least one embodiment, tensor cores are configured to perform deep learning matrix arithmetic, such as convolution operations for neural network training and inferencing. In at least one embodiment, each tensor core operates on a 4×4 matrix and performs a matrix multiply and accumulate operation, D=A×B+C, where A, B, C, and D are 4×4 matrices.

In at least one embodiment, matrix multiply inputs A and B are 16-bit floating point matrices and accumulation matrices C and D are 16-bit floating point or 32-bit floating point matrices. In at least one embodiment, tensor cores operate on 16-bit floating point input data with 32-bit floating point accumulation. In at least one embodiment, 16-bit floating point multiply uses 64 operations and results in a full precision product that is then accumulated using 32-bit floating point addition with other intermediate products for a 4×4×4 matrix multiply. Tensor cores are used to perform much larger two-dimensional or higher dimensional matrix operations, built up from these smaller elements, in at least one embodiment. In at least one embodiment, an API, such as a CUDA 9 C++ API, exposes specialized matrix load, matrix multiply and accumulate, and matrix store operations to efficiently use tensor cores from a CUDA-C++ program. In at least one embodiment, at a CUDA level, a warp-level interface assumes 16×16 size matrices spanning all 32 threads of warp.

In at least one embodiment, each SM 4400 comprises, without limitation, M SFUs 4412 that perform special functions (e.g., attribute evaluation, reciprocal square root, and like). In at least one embodiment, SFUs 4412 include, without limitation, a tree traversal unit configured to traverse a hierarchical tree data structure. In at least one embodiment, SFUs 4412 include, without limitation, a texture unit configured to perform texture map filtering operations. In at least one embodiment, texture units are configured to load texture maps (e.g., a 2D array of texels) from memory and sample texture maps to produce sampled texture values for use in shader programs executed by SM 4400. In at least one embodiment, texture maps are stored in shared memory/L1 cache 4418. In at least one embodiment, texture units implement texture operations such as filtering operations using mip-maps (e.g., texture maps of varying levels of detail), in accordance with at least one embodiment. In at least one embodiment, each SM 4400 includes, without limitation, two texture units.

Each SM 4400 comprises, without limitation, N LSUs 4414 that implement load and store operations between shared memory/L1 cache 4418 and register file 4408, in at least one embodiment. Interconnect network 4416 connects each functional unit to register file 4408 and LSU 4414 to register file 4408 and shared memory/L1 cache 4418 in at least one embodiment. In at least one embodiment, interconnect network 4416 is a crossbar that can be configured to connect any functional units to any registers in register file 4408 and connect LSUs 4414 to register file 4408 and memory locations in shared memory/L1 cache 4418.

In at least one embodiment, shared memory/L1 cache 4418 is an array of on-chip memory that allows for data storage and communication between SM 4400 and primitive engine and between threads in SM 4400, in at least one embodiment. In at least one embodiment, shared memory/L1 cache 4418 comprises, without limitation, 128 KB of storage capacity and is in a path from SM 4400 to a partition unit. In at least one embodiment, shared memory/L1 cache 4418, in at least one embodiment, is used to cache reads and writes. In at least one embodiment, one or more of shared memory/L1 cache 4418, L2 cache, and memory are backing stores.

Combining data cache and shared memory functionality into a single memory block provides improved performance for both types of memory accesses, in at least one embodiment. In at least one embodiment, capacity is used or is usable as a cache by programs that do not use shared memory, such as if shared memory is configured to use half of a capacity, and texture and load/store operations can use remaining capacity. Integration within shared memory/L1 cache 4418 enables shared memory/L1 cache 4418 to function as a high-throughput conduit for streaming data while simultaneously providing high-bandwidth and low-latency access to frequently reused data, in accordance with at least one embodiment. In at least one embodiment, when configured for general purpose parallel computation, a simpler configuration can be used compared with graphics processing. In at least one embodiment, fixed function graphics processing units are bypassed, creating a much simpler programming model. In a general purpose parallel computation configuration, a work distribution unit assigns and distributes blocks of threads directly to DPCs, in at least one embodiment. In at least one embodiment, threads in a block execute a common program, using a unique thread ID in calculation to ensure each thread generates unique results, using SM 4400 to execute program and perform calculations, shared memory/L1 cache 4418 to communicate between threads, and LSU 4414 to read and write global memory through shared memory/L1 cache 4418 and memory partition unit. In at least one embodiment, when configured for general purpose parallel computation, SM 4400 writes commands that scheduler unit 4404 can use to launch new work on DPCs.

In at least one embodiment, a PPU is included in or coupled to a desktop computer, a laptop computer, a tablet computer, servers, supercomputers, a smart-phone (e.g., a wireless, hand-held device), personal digital assistant (“PDA”), a digital camera, a vehicle, a head mounted display, a hand-held electronic device, and more. In at least one embodiment, a PPU is embodied on a single semiconductor substrate. In at least one embodiment, a PPU is included in a system-on-a-chip (“SoC”) along with one or more other devices such as additional PPUs, memory, a reduced instruction set computer (“RISC”) CPU, a memory management unit (“MMU”), a digital-to-analog converter (“DAC”), and like.

In at least one embodiment, a PPU may be included on a graphics card that includes one or more memory devices. In at least one embodiment, that graphics card may be configured to interface with a PCIe slot on a motherboard of a desktop computer. In at least one embodiment, that PPU may be an integrated graphics processing unit (“iGPU”) included in chipset of a motherboard.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B. In at least one embodiment, deep learning application processor is used to train a machine learning model, such as a neural network, to predict or infer information provided to SM 4400. In at least one embodiment, SM 4400 is used to infer or predict information based on a trained machine learning model (e.g., neural network) that has been trained by another processor or system or by SM 4400. In at least one embodiment, SM 4400 may be used to perform one or more neural network use cases described herein.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

Embodiments are disclosed related a virtualized computing platform for advanced computing, such as image inferencing and image processing in medical applications. Without limitation, embodiments may include radiography, magnetic resonance imaging (MRI), nuclear medicine, ultrasound, sonography, elastography, photoacoustic imaging, tomography, echocardiography, functional near-infrared spectroscopy, and magnetic particle imaging, or a combination thereof. In at least one embodiment, a virtualized computing platform and associated processes described herein may additionally or alternatively be used, without limitation, in forensic science analysis, sub-surface detection and imaging (e.g., oil exploration, archaeology, paleontology, etc.), topography, oceanography, geology, osteology, meteorology, intelligent area or object tracking and monitoring, sensor data processing (e.g., RADAR, SONAR, LIDAR, etc.), and/or genomics and gene sequencing.

With reference to FIG. 45 , FIG. 45 is an example data flow diagram for a process 4500 of generating and deploying an image processing and inferencing pipeline, in accordance with at least one embodiment. In at least one embodiment, process 4500 may be deployed for use with imaging devices, processing devices, genomics devices, gene sequencing devices, radiology devices, and/or other device types at one or more facilities 4502, such as medical facilities, hospitals, healthcare institutes, clinics, research or diagnostic labs, etc. In at least one embodiment, process 4500 may be deployed to perform genomics analysis and inferencing on sequencing data. Examples of genomic analyses that may be performed using systems and processes described herein include, without limitation, variant calling, mutation detection, and gene expression quantification.

In at least one embodiment, process 4500 may be executed within a training system 4504 and/or a deployment system 4506. In at least one embodiment, training system 4504 may be used to perform training, deployment, and implementation of machine learning models (e.g., neural networks, object detection algorithms, computer vision algorithms, etc.) for use in deployment system 4506. In at least one embodiment, deployment system 4506 may be configured to offload processing and compute resources among a distributed computing environment to reduce infrastructure requirements at facility 4502. In at least one embodiment, deployment system 4506 may provide a streamlined platform for selecting, customizing, and implementing virtual instruments for use with imaging devices (e.g., MRI, CT Scan, X-Ray, Ultrasound, etc.) or sequencing devices at facility 4502. In at least one embodiment, virtual instruments may include software-defined applications for performing one or more processing operations with respect to imaging data generated by imaging devices, sequencing devices, radiology devices, and/or other device types. In at least one embodiment, one or more applications in a pipeline may use or call upon services (e.g., inference, visualization, compute, AI, etc.) of deployment system 4506 during execution of applications.

In at least one embodiment, some of applications used in advanced processing and inferencing pipelines may use machine learning models or other AI to perform one or more processing steps. In at least one embodiment, machine learning models may be trained at facility 4502 using data 4508 (such as imaging data) generated at facility 4502 (and stored on one or more picture archiving and communication system (PACS) servers at facility 4502), may be trained using imaging or sequencing data 4508 from another facility or facilities (e.g., a different hospital, lab, clinic, etc.), or a combination thereof. In at least one embodiment, training system 4504 may be used to provide applications, services, and/or other resources for generating working, deployable machine learning models for deployment system 4506.

In at least one embodiment, a model registry 4524 may be backed by object storage that may support versioning and object metadata. In at least one embodiment, object storage may be accessible through, for example, a cloud storage (e.g., a cloud 4626 of FIG. 46 ) compatible application programming interface (API) from within a cloud platform. In at least one embodiment, machine learning models within model registry 4524 may uploaded, listed, modified, or deleted by developers or partners of a system interacting with an API. In at least one embodiment, an API may provide access to methods that allow users with appropriate credentials to associate models with applications, such that models may be executed as part of execution of containerized instantiations of applications.

In at least one embodiment, a training pipeline 4604 (FIG. 46 ) may include a scenario where facility 4502 is training their own machine learning model, or has an existing machine learning model that needs to be optimized or updated. In at least one embodiment, imaging data 4508 generated by imaging device(s), sequencing devices, and/or other device types may be received. In at least one embodiment, once imaging data 4508 is received, AI-assisted annotation 4510 may be used to aid in generating annotations corresponding to imaging data 4508 to be used as ground truth data for a machine learning model. In at least one embodiment, AI-assisted annotation 4510 may include one or more machine learning models (e.g., convolutional neural networks (CNNs)) that may be trained to generate annotations corresponding to certain types of imaging data 4508 (e.g., from certain devices) and/or certain types of anomalies in imaging data 4508. In at least one embodiment, AI-assisted annotations 4510 may then be used directly, or may be adjusted or fine-tuned using an annotation tool (e.g., by a researcher, a clinician, a doctor, a scientist, etc.), to generate ground truth data. In at least one embodiment, in some examples, labeled clinic data 4512 (e.g., annotations provided by a clinician, doctor, scientist, technician, etc.) may be used as ground truth data for training a machine learning model. In at least one embodiment, AI-assisted annotations 4510, labeled clinic data 4512, or a combination thereof may be used as ground truth data for training a machine learning model. In at least one embodiment, a trained machine learning model may be referred to as an output model 4516, and may be used by deployment system 4506, as described herein.

In at least one embodiment, training pipeline 4604 (FIG. 46 ) may include a scenario where facility 4502 needs a machine learning model for use in performing one or more processing tasks for one or more applications in deployment system 4506, but facility 4502 may not currently have such a machine learning model (or may not have a model that is optimized, efficient, or effective for such purposes). In at least one embodiment, an existing machine learning model may be selected from model registry 4524. In at least one embodiment, model registry 4524 may include machine learning models trained to perform a variety of different inference tasks on imaging data. In at least one embodiment, machine learning models in model registry 4524 may have been trained on imaging data from different facilities than facility 4502 (e.g., facilities remotely located). In at least one embodiment, machine learning models may have been trained on imaging data from one location, two locations, or any number of locations. In at least one embodiment, when being trained on imaging data from a specific location, training may take place at that location, or at least in a manner that protects confidentiality of imaging data or restricts imaging data from being transferred off-premises (e.g., to comply with HIPAA regulations, privacy regulations, etc.). In at least one embodiment, once a model is trained—or partially trained—at one location, a machine learning model may be added to model registry 4524. In at least one embodiment, a machine learning model may then be retrained, or updated, at any number of other facilities, and a retrained or updated model may be made available in model registry 4524. In at least one embodiment, a machine learning model may then be selected from model registry 4524—and referred to as output model 4516—and may be used in deployment system 4506 to perform one or more processing tasks for one or more applications of a deployment system.

In at least one embodiment, training pipeline 4604 (FIG. 46 ) may be used in a scenario that includes facility 4502 requiring a machine learning model for use in performing one or more processing tasks for one or more applications in deployment system 4506, but facility 4502 may not currently have such a machine learning model (or may not have a model that is optimized, efficient, or effective for such purposes). In at least one embodiment, a machine learning model selected from model registry 4524 might not be fine-tuned or optimized for imaging data 4508 generated at facility 4502 because of differences in populations, genetic variations, robustness of training data used to train a machine learning model, diversity in anomalies of training data, and/or other issues with training data. In at least one embodiment, AI-assisted annotation 4510 may be used to aid in generating annotations corresponding to imaging data 4508 to be used as ground truth data for retraining or updating a machine learning model. In at least one embodiment, labeled clinic data 4512 (e.g., annotations provided by a clinician, doctor, scientist, etc.) may be used as ground truth data for training a machine learning model. In at least one embodiment, retraining or updating a machine learning model may be referred to as model training 4514. In at least one embodiment, model training 4514—e.g., AI-assisted annotations 4510, labeled clinic data 4512, or a combination thereof—may be used as ground truth data for retraining or updating a machine learning model.

In at least one embodiment, deployment system 4506 may include software 4518, services 4520, hardware 4522, and/or other components, features, and functionality. In at least one embodiment, deployment system 4506 may include a software “stack,” such that software 4518 may be built on top of services 4520 and may use services 4520 to perform some or all of processing tasks, and services 4520 and software 4518 may be built on top of hardware 4522 and use hardware 4522 to execute processing, storage, and/or other compute tasks of deployment system 4506.

In at least one embodiment, software 4518 may include any number of different containers, where each container may execute an instantiation of an application. In at least one embodiment, each application may perform one or more processing tasks in an advanced processing and inferencing pipeline (e.g., inferencing, object detection, feature detection, segmentation, image enhancement, calibration, etc.). In at least one embodiment, for each type of imaging device (e.g., CT, MRI, X-Ray, ultrasound, sonography, echocardiography, etc.), sequencing device, radiology device, genomics device, etc., there may be any number of containers that may perform a data processing task with respect to imaging data 4508 (or other data types, such as those described herein) generated by a device. In at least one embodiment, an advanced processing and inferencing pipeline may be defined based on selections of different containers that are desired or required for processing imaging data 4508, in addition to containers that receive and configure imaging data for use by each container and/or for use by facility 4502 after processing through a pipeline (e.g., to convert outputs back to a usable data type, such as digital imaging and communications in medicine (DICOM) data, radiology information system (RIS) data, clinical information system (CIS) data, remote procedure call (RPC) data, data substantially compliant with a representation state transfer (REST) interface, data substantially compliant with a file-based interface, and/or raw data, for storage and display at facility 4502). In at least one embodiment, a combination of containers within software 4518 (e.g., that make up a pipeline) may be referred to as a virtual instrument (as described in more detail herein), and a virtual instrument may leverage services 4520 and hardware 4522 to execute some or all processing tasks of applications instantiated in containers.

In at least one embodiment, a data processing pipeline may receive input data (e.g., imaging data 4508) in a DICOM, RIS, CIS, REST compliant, RPC, raw, and/or other format in response to an inference request (e.g., a request from a user of deployment system 4506, such as a clinician, a doctor, a radiologist, etc.). In at least one embodiment, input data may be representative of one or more images, video, and/or other data representations generated by one or more imaging devices, sequencing devices, radiology devices, genomics devices, and/or other device types. In at least one embodiment, data may undergo pre-processing as part of data processing pipeline to prepare data for processing by one or more applications. In at least one embodiment, post-processing may be performed on an output of one or more inferencing tasks or other processing tasks of a pipeline to prepare an output data for a next application and/or to prepare output data for transmission and/or use by a user (e.g., as a response to an inference request). In at least one embodiment, inferencing tasks may be performed by one or more machine learning models, such as trained or deployed neural networks, which may include output models 4516 of training system 4504.

In at least one embodiment, tasks of data processing pipeline may be encapsulated in a container(s) that each represent a discrete, fully functional instantiation of an application and virtualized computing environment that is able to reference machine learning models. In at least one embodiment, containers or applications may be published into a private (e.g., limited access) area of a container registry (described in more detail herein), and trained or deployed models may be stored in model registry 4524 and associated with one or more applications. In at least one embodiment, images of applications (e.g., container images) may be available in a container registry, and once selected by a user from a container registry for deployment in a pipeline, an image may be used to generate a container for an instantiation of an application for use by a user's system.

In at least one embodiment, developers (e.g., software developers, clinicians, doctors, etc.) may develop, publish, and store applications (e.g., as containers) for performing image processing and/or inferencing on supplied data. In at least one embodiment, development, publishing, and/or storing may be performed using a software development kit (SDK) associated with a system (e.g., to ensure that an application and/or container developed is compliant with or compatible with a system). In at least one embodiment, an application that is developed may be tested locally (e.g., at a first facility, on data from a first facility) with an SDK which may support at least some of services 4520 as a system (e.g., system 4600 of FIG. 46 ). In at least one embodiment, because DICOM objects may contain anywhere from one to hundreds of images or other data types, and due to a variation in data, a developer may be responsible for managing (e.g., setting constructs for, building pre-processing into an application, etc.) extraction and preparation of incoming DICOM data. In at least one embodiment, once validated by system 4600 (e.g., for accuracy, safety, patient privacy, etc.), an application may be available in a container registry for selection and/or implementation by a user (e.g., a hospital, clinic, lab, healthcare provider, etc.) to perform one or more processing tasks with respect to data at a facility (e.g., a second facility) of a user.

In at least one embodiment, developers may then share applications or containers through a network for access and use by users of a system (e.g., system 4600 of FIG. 46 ). In at least one embodiment, completed and validated applications or containers may be stored in a container registry and associated machine learning models may be stored in model registry 4524. In at least one embodiment, a requesting entity (e.g., a user at a medical facility)—who provides an inference or image processing request—may browse a container registry and/or model registry 4524 for an application, container, dataset, machine learning model, etc., select a desired combination of elements for inclusion in data processing pipeline, and submit an imaging processing request. In at least one embodiment, a request may include input data (and associated patient data, in some examples) that is necessary to perform a request, and/or may include a selection of application(s) and/or machine learning models to be executed in processing a request. In at least one embodiment, a request may then be passed to one or more components of deployment system 4506 (e.g., a cloud) to perform processing of data processing pipeline. In at least one embodiment, processing by deployment system 4506 may include referencing selected elements (e.g., applications, containers, models, etc.) from a container registry and/or model registry 4524. In at least one embodiment, once results are generated by a pipeline, results may be returned to a user for reference (e.g., for viewing in a viewing application suite executing on a local, on-premises workstation or terminal). In at least one embodiment, a radiologist may receive results from an data processing pipeline including any number of application and/or containers, where results may include anomaly detection in X-rays, CT scans, MRIs, etc.

In at least one embodiment, to aid in processing or execution of applications or containers in pipelines, services 4520 may be leveraged. In at least one embodiment, services 4520 may include compute services, artificial intelligence (AI) services, visualization services, and/or other service types. In at least one embodiment, services 4520 may provide functionality that is common to one or more applications in software 4518, so functionality may be abstracted to a service that may be called upon or leveraged by applications. In at least one embodiment, functionality provided by services 4520 may run dynamically and more efficiently, while also scaling well by allowing applications to process data in parallel (e.g., using a parallel computing platform 4630 (FIG. 46 )). In at least one embodiment, rather than each application that shares a same functionality offered by a service 4520 being required to have a respective instance of service 4520, service 4520 may be shared between and among various applications. In at least one embodiment, services may include an inference server or engine that may be used for executing detection or segmentation tasks, as non-limiting examples. In at least one embodiment, a model training service may be included that may provide machine learning model training and/or retraining capabilities. In at least one embodiment, a data augmentation service may further be included that may provide GPU accelerated data (e.g., DICOM, RIS, CIS, REST compliant, RPC, raw, etc.) extraction, resizing, scaling, and/or other augmentation. In at least one embodiment, a visualization service may be used that may add image rendering effects—such as ray-tracing, rasterization, denoising, sharpening, etc.—to add realism to two-dimensional (2D) and/or three-dimensional (3D) models. In at least one embodiment, virtual instrument services may be included that provide for beam-forming, segmentation, inferencing, imaging, and/or support for other applications within pipelines of virtual instruments.

In at least one embodiment, where a service 4520 includes an AI service (e.g., an inference service), one or more machine learning models associated with an application for anomaly detection (e.g., tumors, growth abnormalities, scarring, etc.) may be executed by calling upon (e.g., as an API call) an inference service (e.g., an inference server) to execute machine learning model(s), or processing thereof, as part of application execution. In at least one embodiment, where another application includes one or more machine learning models for segmentation tasks, an application may call upon an inference service to execute machine learning models for performing one or more of processing operations associated with segmentation tasks. In at least one embodiment, software 4518 implementing advanced processing and inferencing pipeline that includes segmentation application and anomaly detection application may be streamlined because each application may call upon a same inference service to perform one or more inferencing tasks.

In at least one embodiment, hardware 4522 may include GPUs, CPUs, graphics cards, an AI/deep learning system (e.g., an AI supercomputer, such as NVIDIA's DGX supercomputer system), a cloud platform, or a combination thereof. In at least one embodiment, different types of hardware 4522 may be used to provide efficient, purpose-built support for software 4518 and services 4520 in deployment system 4506. In at least one embodiment, use of GPU processing may be implemented for processing locally (e.g., at facility 4502), within an AI/deep learning system, in a cloud system, and/or in other processing components of deployment system 4506 to improve efficiency, accuracy, and efficacy of image processing, image reconstruction, segmentation, MRI exams, stroke or heart attack detection (e.g., in real-time), image quality in rendering, etc. In at least one embodiment, a facility may include imaging devices, genomics devices, sequencing devices, and/or other device types on-premises that may leverage GPUs to generate imaging data representative of a subject's anatomy.

In at least one embodiment, software 4518 and/or services 4520 may be optimized for GPU processing with respect to deep learning, machine learning, and/or high-performance computing, as non-limiting examples. In at least one embodiment, at least some of computing environment of deployment system 4506 and/or training system 4504 may be executed in a datacenter one or more supercomputers or high performance computing systems, with GPU optimized software (e.g., hardware and software combination of NVIDIA's DGX system). In at least one embodiment, datacenters may be compliant with provisions of HIPAA, such that receipt, processing, and transmission of imaging data and/or other patient data is securely handled with respect to privacy of patient data. In at least one embodiment, hardware 4522 may include any number of GPUs that may be called upon to perform processing of data in parallel, as described herein. In at least one embodiment, cloud platform may further include GPU processing for GPU-optimized execution of deep learning tasks, machine learning tasks, or other computing tasks. In at least one embodiment, cloud platform (e.g., NVIDIA's NGC) may be executed using an AI/deep learning supercomputer(s) and/or GPU-optimized software (e.g., as provided on NVIDIA's DGX systems) as a hardware abstraction and scaling platform. In at least one embodiment, cloud platform may integrate an application container clustering system or orchestration system (e.g., KUBERNETES) on multiple GPUs to enable seamless scaling and load balancing.

In at least on embodiment, a system that determines a grasp pose can be constructed using a processor as shown and described above. In at least one embodiment, the processor executes executable instructions that cause the processor to determine and refine grasp poses as described herein.

FIG. 46 is a system diagram for an example system 4600 for generating and deploying an imaging deployment pipeline, in accordance with at least one embodiment. In at least one embodiment, system 4600 may be used to implement process 4500 of FIG. 45 and/or other processes including advanced processing and inferencing pipelines. In at least one embodiment, system 4600 may include training system 4504 and deployment system 4506. In at least one embodiment, training system 4504 and deployment system 4506 may be implemented using software 4518, services 4520, and/or hardware 4522, as described herein.

In at least one embodiment, system 4600 (e.g., training system 4504 and/or deployment system 4506) may implemented in a cloud computing environment (e.g., using cloud 4626). In at least one embodiment, system 4600 may be implemented locally with respect to a healthcare services facility, or as a combination of both cloud and local computing resources. In at least one embodiment, in embodiments where cloud computing is implemented, patient data may be separated from, or unprocessed by, by one or more components of system 4600 that would render processing non-compliant with HIPAA and/or other data handling and privacy regulations or laws. In at least one embodiment, access to APIs in cloud 4626 may be restricted to authorized users through enacted security measures or protocols. In at least one embodiment, a security protocol may include web tokens that may be signed by an authentication (e.g., AuthN, AuthZ, Gluecon, etc.) service and may carry appropriate authorization. In at least one embodiment, APIs of virtual instruments (described herein), or other instantiations of system 4600, may be restricted to a set of public IPs that have been vetted or authorized for interaction.

In at least one embodiment, various components of system 4600 may communicate between and among one another using any of a variety of different network types, including but not limited to local area networks (LANs) and/or wide area networks (WANs) via wired and/or wireless communication protocols. In at least one embodiment, communication between facilities and components of system 4600 (e.g., for transmitting inference requests, for receiving results of inference requests, etc.) may be communicated over a data bus or data busses, wireless data protocols (Wi-Fi), wired data protocols (e.g., Ethernet), etc.

In at least one embodiment, training system 4504 may execute training pipelines 4604, similar to those described herein with respect to FIG. 45 . In at least one embodiment, where one or more machine learning models are to be used in deployment pipelines 4610 by deployment system 4506, training pipelines 4604 may be used to train or retrain one or more (e.g., pre-trained) models, and/or implement one or more of pre-trained models 4606 (e.g., without a need for retraining or updating). In at least one embodiment, as a result of training pipelines 4604, output model(s) 4516 may be generated. In at least one embodiment, training pipelines 4604 may include any number of processing steps, such as but not limited to imaging data (or other input data) conversion or adaption (e.g., using DICOM adapter 4602A to convert DICOM images to another format suitable for processing by respective machine learning models, such as Neuroimaging Informatics Technology Initiative (NIfTI) format), AI-assisted annotation 4510, labeling or annotating of imaging data 4508 to generate labeled clinic data 4512, model selection from a model registry, model training 4514, training, retraining, or updating models, and/or other processing steps. In at least one embodiment, for different machine learning models used by deployment system 4506, different training pipelines 4604 may be used. In at least one embodiment, training pipeline 4604 similar to a first example described with respect to FIG. 45 may be used for a first machine learning model, training pipeline 4604 similar to a second example described with respect to FIG. 45 may be used for a second machine learning model, and training pipeline 4604 similar to a third example described with respect to FIG. 45 may be used for a third machine learning model. In at least one embodiment, any combination of tasks within training system 4504 may be used depending on what is required for each respective machine learning model. In at least one embodiment, one or more of machine learning models may already be trained and ready for deployment so machine learning models may not undergo any processing by training system 4504, and may be implemented by deployment system 4506.

In at least one embodiment, output model(s) 4516 and/or pre-trained model(s) 4606 may include any types of machine learning models depending on implementation or embodiment. In at least one embodiment, and without limitation, machine learning models used by system 4600 may include machine learning model(s) using linear regression, logistic regression, decision trees, support vector machines (SVM), Naïve Bayes, k-nearest neighbor (Knn), K means clustering, random forest, dimensionality reduction algorithms, gradient boosting algorithms, neural networks (e.g., auto-encoders, convolutional, recurrent, perceptrons, Long/Short Term Memory (LSTM), Hopfield, Boltzmann, deep belief, deconvolutional, generative adversarial, liquid state machine, etc.), and/or other types of machine learning models.

In at least one embodiment, training pipelines 4604 may include AI-assisted annotation, as described in more detail herein with respect to at least FIG. 49B. In at least one embodiment, labeled clinic data 4512 (e.g., traditional annotation) may be generated by any number of techniques. In at least one embodiment, labels or other annotations may be generated within a drawing program (e.g., an annotation program), a computer aided design (CAD) program, a labeling program, another type of program suitable for generating annotations or labels for ground truth, and/or may be hand drawn, in some examples. In at least one embodiment, ground truth data may be synthetically produced (e.g., generated from computer models or renderings), real produced (e.g., designed and produced from real-world data), machine-automated (e.g., using feature analysis and learning to extract features from data and then generate labels), human annotated (e.g., labeler, or annotation expert, defines location of labels), and/or a combination thereof. In at least one embodiment, for each instance of imaging data 4508 (or other data type used by machine learning models), there may be corresponding ground truth data generated by training system 4504. In at least one embodiment, AI-assisted annotation may be performed as part of deployment pipelines 4610; either in addition to, or in lieu of AI-assisted annotation included in training pipelines 4604. In at least one embodiment, system 4600 may include a multi-layer platform that may include a software layer (e.g., software 4518) of diagnostic applications (or other application types) that may perform one or more medical imaging and diagnostic functions. In at least one embodiment, system 4600 may be communicatively coupled to (e.g., via encrypted links) PACS server networks of one or more facilities. In at least one embodiment, system 4600 may be configured to access and referenced data (e.g., DICOM data, RIS data, raw data, CIS data, REST compliant data, RPC data, raw data, etc.) from PACS servers (e.g., via a DICOM adapter 4602, or another data type adapter such as RIS, CIS, REST compliant, RPC, raw, etc.) to perform operations, such as training machine learning models, deploying machine learning models, image processing, inferencing, and/or other operations.

In at least one embodiment, a software layer may be implemented as a secure, encrypted, and/or authenticated API through which applications or containers may be invoked (e.g., called) from an external environment(s) (e.g., facility 4502). In at least one embodiment, applications may then call or execute one or more services 4520 for performing compute, AI, or visualization tasks associated with respective applications, and software 4518 and/or services 4520 may leverage hardware 4522 to perform processing tasks in an effective and efficient manner.

In at least one embodiment, deployment system 4506 may execute deployment pipelines 4610. In at least one embodiment, deployment pipelines 4610 may include any number of applications that may be sequentially, non-sequentially, or otherwise applied to imaging data (and/or other data types) generated by imaging devices, sequencing devices, genomics devices, etc.—including AI-assisted annotation, as described above. In at least one embodiment, as described herein, a deployment pipeline 4610 for an individual device may be referred to as a virtual instrument for a device (e.g., a virtual ultrasound instrument, a virtual CT scan instrument, a virtual sequencing instrument, etc.). In at least one embodiment, for a single device, there may be more than one deployment pipeline 4610 depending on information desired from data generated by a device. In at least one embodiment, where detections of anomalies are desired from an MRI machine, there may be a first deployment pipeline 4610, and where image enhancement is desired from output of an MRI machine, there may be a second deployment pipeline 4610.

In at least one embodiment, applications available for deployment pipelines 4610 may include any application that may be used for performing processing tasks on imaging data or other data from devices. In at least one embodiment, different applications may be responsible for image enhancement, segmentation, reconstruction, anomaly detection, object detection, feature detection, treatment planning, dosimetry, beam planning (or other radiation treatment procedures), and/or other analysis, image processing, or inferencing tasks. In at least one embodiment, deployment system 4506 may define constructs for each of applications, such that users of deployment system 4506 (e.g., medical facilities, labs, clinics, etc.) may understand constructs and adapt applications for implementation within their respective facility. In at least one embodiment, an application for image reconstruction may be selected for inclusion in deployment pipeline 4610, but data type generated by an imaging device may be different from a data type used within an application. In at least one embodiment, DICOM adapter 4602B (and/or a DICOM reader) or another data type adapter or reader (e.g., RIS, CIS, REST compliant, RPC, raw, etc.) may be used within deployment pipeline 4610 to convert data to a form useable by an application within deployment system 4506. In at least one embodiment, access to DICOM, RIS, CIS, REST compliant, RPC, raw, and/or other data type libraries may be accumulated and pre-processed, including decoding, extracting, and/or performing any convolutions, color corrections, sharpness, gamma, and/or other augmentations to data. In at least one embodiment, DICOM, RIS, CIS, REST compliant, RPC, and/or raw data may be unordered and a pre-pass may be executed to organize or sort collected data. In at least one embodiment, because various applications may share common image operations, in some embodiments, a data augmentation library (e.g., as one of services 4520) may be used to accelerate these operations. In at least one embodiment, to avoid bottlenecks of conventional processing approaches that rely on CPU processing, parallel computing platform 4630 may be used for GPU acceleration of these processing tasks.

In at least one embodiment, an image reconstruction application may include a processing task that includes use of a machine learning model. In at least one embodiment, a user may desire to use their own machine learning model, or to select a machine learning model from model registry 4524. In at least one embodiment, a user may implement their own machine learning model or select a machine learning model for inclusion in an application for performing a processing task. In at least one embodiment, applications may be selectable and customizable, and by defining constructs of applications, deployment and implementation of applications for a particular user are presented as a more seamless user experience. In at least one embodiment, by leveraging other features of system 4600—such as services 4520 and hardware 4522—deployment pipelines 4610 may be even more user friendly, provide for easier integration, and produce more accurate, efficient, and timely results.

In at least one embodiment, deployment system 4506 may include a user interface 4614 (e.g., a graphical user interface, a web interface, etc.) that may be used to select applications for inclusion in deployment pipeline(s) 4610, arrange applications, modify or change applications or parameters or constructs thereof, use and interact with deployment pipeline(s) 4610 during set-up and/or deployment, and/or to otherwise interact with deployment system 4506. In at least one embodiment, although not illustrated with respect to training system 4504, user interface 4614 (or a different user interface) may be used for selecting models for use in deployment system 4506, for selecting models for training, or retraining, in training system 4504, and/or for otherwise interacting with training system 4504.

In at least one embodiment, pipeline manager 4612 may be used, in addition to an application orchestration system 4628, to manage interaction between applications or containers of deployment pipeline(s) 4610 and services 4520 and/or hardware 4522. In at least one embodiment, pipeline manager 4612 may be configured to facilitate interactions from application to application, from application to service 4520, and/or from application or service to hardware 4522. In at least one embodiment, although illustrated as included in software 4518, this is not intended to be limiting, and in some examples (e.g., as illustrated in FIG. 47 ) pipeline manager 4612 may be included in services 4520. In at least one embodiment, application orchestration system 4628 (e.g., Kubernetes, DOCKER, etc.) may include a container orchestration system that may group applications into containers as logical units for coordination, management, scaling, and deployment. In at least one embodiment, by associating applications from deployment pipeline(s) 4610 (e.g., a reconstruction application, a segmentation application, etc.) with individual containers, each application may execute in a self-contained environment (e.g., at a kernel level) to increase speed and efficiency.

In at least one embodiment, each application and/or container (or image thereof) may be individually developed, modified, and deployed (e.g., a first user or developer may develop, modify, and deploy a first application and a second user or developer may develop, modify, and deploy a second application separate from a first user or developer), which may allow for focus on, and attention to, a task of a single application and/or container(s) without being hindered by tasks of another application(s) or container(s). In at least one embodiment, communication, and cooperation between different containers or applications may be aided by pipeline manager 4612 and application orchestration system 4628. In at least one embodiment, so long as an expected input and/or output of each container or application is known by a system (e.g., based on constructs of applications or containers), application orchestration system 4628 and/or pipeline manager 4612 may facilitate communication among and between, and sharing of resources among and between, each of applications or containers. In at least one embodiment, because one or more of applications or containers in deployment pipeline(s) 4610 may share same services and resources, application orchestration system 4628 may orchestrate, load balance, and determine sharing of services or resources between and among various applications or containers. In at least one embodiment, a scheduler may be used to track resource requirements of applications or containers, current usage or planned usage of these resources, and resource availability. In at least one embodiment, a scheduler may thus allocate resources to different applications and distribute resources between and among applications in view of requirements and availability of a system. In some examples, a scheduler (and/or other component of application orchestration system 4628) may determine resource availability and distribution based on constraints imposed on a system (e.g., user constraints), such as quality of service (QoS), urgency of need for data outputs (e.g., to determine whether to execute real-time processing or delayed processing), etc.

In at least one embodiment, services 4520 leveraged by and shared by applications or containers in deployment system 4506 may include compute services 4616, AI services 4618, visualization services 4620, and/or other service types. In at least one embodiment, applications may call (e.g., execute) one or more of services 4520 to perform processing operations for an application. In at least one embodiment, compute services 4616 may be leveraged by applications to perform super-computing or other high-performance computing (HPC) tasks. In at least one embodiment, compute service(s) 4616 may be leveraged to perform parallel processing (e.g., using a parallel computing platform 4630) for processing data through one or more of applications and/or one or more tasks of a single application, substantially simultaneously. In at least one embodiment, parallel computing platform 4630 (e.g., NVIDIA's CUDA) may enable general purpose computing on GPUs (GPGPU) (e.g., GPUs 4622). In at least one embodiment, a software layer of parallel computing platform 4630 may provide access to virtual instruction sets and parallel computational elements of GPUs, for execution of compute kernels. In at least one embodiment, parallel computing platform 4630 may include memory and, in some embodiments, a memory may be shared between and among multiple containers, and/or between and among different processing tasks within a single container. In at least one embodiment, inter-process communication (IPC) calls may be generated for multiple containers and/or for multiple processes within a container to use same data from a shared segment of memory of parallel computing platform 4630 (e.g., where multiple different stages of an application or multiple applications are processing same information). In at least one embodiment, rather than making a copy of data and moving data to different locations in memory (e.g., a read/write operation), same data in same location of a memory may be used for any number of processing tasks (e.g., at a same time, at different times, etc.). In at least one embodiment, as data is used to generate new data as a result of processing, this information of a new location of data may be stored and shared between various applications. In at least one embodiment, location of data and a location of updated or modified data may be part of a definition of how a payload is understood within containers.

In at least one embodiment, AI services 4618 may be leveraged to perform inferencing services for executing machine learning model(s) associated with applications (e.g., tasked with performing one or more processing tasks of an application). In at least one embodiment, AI services 4618 may leverage AI system 4624 to execute machine learning model(s) (e.g., neural networks, such as CNNs) for segmentation, reconstruction, object detection, feature detection, classification, and/or other inferencing tasks. In at least one embodiment, applications of deployment pipeline(s) 4610 may use one or more of output models 4516 from training system 4504 and/or other models of applications to perform inference on imaging data (e.g., DICOM data, RIS data, CIS data, REST compliant data, RPC data, raw data, etc.). In at least one embodiment, two or more examples of inferencing using application orchestration system 4628 (e.g., a scheduler) may be available. In at least one embodiment, a first category may include a high priority/low latency path that may achieve higher service level agreements, such as for performing inference on urgent requests during an emergency, or for a radiologist during diagnosis. In at least one embodiment, a second category may include a standard priority path that may be used for requests that may be non-urgent or where analysis may be performed at a later time. In at least one embodiment, application orchestration system 4628 may distribute resources (e.g., services 4520 and/or hardware 4522) based on priority paths for different inferencing tasks of AI services 4618.

In at least one embodiment, shared storage may be mounted to AI services 4618 within system 4600. In at least one embodiment, shared storage may operate as a cache (or other storage device type) and may be used to process inference requests from applications. In at least one embodiment, when an inference request is submitted, a request may be received by a set of API instances of deployment system 4506, and one or more instances may be selected (e.g., for best fit, for load balancing, etc.) to process a request. In at least one embodiment, to process a request, a request may be entered into a database, a machine learning model may be located from model registry 4524 if not already in a cache, a validation step may ensure appropriate machine learning model is loaded into a cache (e.g., shared storage), and/or a copy of a model may be saved to a cache. In at least one embodiment, a scheduler (e.g., of pipeline manager 4612) may be used to launch an application that is referenced in a request if an application is not already running or if there are not enough instances of an application. In at least one embodiment, if an inference server is not already launched to execute a model, an inference server may be launched. In at least one embodiment, any number of inference servers may be launched per model. In at least one embodiment, in a pull model, in which inference servers are clustered, models may be cached whenever load balancing is advantageous. In at least one embodiment, inference servers may be statically loaded in corresponding, distributed servers.

In at least one embodiment, inferencing may be performed using an inference server that runs in a container. In at least one embodiment, an instance of an inference server may be associated with a model (and optionally a plurality of versions of a model). In at least one embodiment, if an instance of an inference server does not exist when a request to perform inference on a model is received, a new instance may be loaded. In at least one embodiment, when starting an inference server, a model may be passed to an inference server such that a same container may be used to serve different models so long as inference server is running as a different instance.

In at least one embodiment, during application execution, an inference request for a given application may be received, and a container (e.g., hosting an instance of an inference server) may be loaded (if not already), and a start procedure may be called. In at least one embodiment, pre-processing logic in a container may load, decode, and/or perform any additional pre-processing on incoming data (e.g., using a CPU(s) and/or GPU(s)). In at least one embodiment, once data is prepared for inference, a container may perform inference as necessary on data. In at least one embodiment, this may include a single inference call on one image (e.g., a hand X-ray), or may require inference on hundreds of images (e.g., a chest CT). In at least one embodiment, an application may summarize results before completing, which may include, without limitation, a single confidence score, pixel level-segmentation, voxel-level segmentation, generating a visualization, or generating text to summarize findings. In at least one embodiment, different models or applications may be assigned different priorities. For example, some models may have a real-time (TAT less than one minute) priority while others may have lower priority (e.g., TAT less than 10 minutes). In at least one embodiment, model execution times may be measured from requesting institution or entity and may include partner network traversal time, as well as execution on an inference service.

In at least one embodiment, transfer of requests between services 4520 and inference applications may be hidden behind a software development kit (SDK), and robust transport may be provide through a queue. In at least one embodiment, a request will be placed in a queue via an API for an individual application/tenant ID combination and an SDK will pull a request from a queue and give a request to an application. In at least one embodiment, a name of a queue may be provided in an environment from where an SDK will pick it up. In at least one embodiment, asynchronous communication through a queue may be useful as it may allow any instance of an application to pick up work as it becomes available. In at least one embodiment, results may be transferred back through a queue, to ensure no data is lost. In at least one embodiment, queues may also provide an ability to segment work, as highest priority work may go to a queue with most instances of an application connected to it, while lowest priority work may go to a queue with a single instance connected to it that processes tasks in an order received. In at least one embodiment, an application may run on a GPU-accelerated instance generated in cloud 4626, and an inference service may perform inferencing on a GPU.

In at least one embodiment, visualization services 4620 may be leveraged to generate visualizations for viewing outputs of applications and/or deployment pipeline(s) 4610. In at least one embodiment, GPUs 4622 may be leveraged by visualization services 4620 to generate visualizations. In at least one embodiment, rendering effects, such as ray-tracing, may be implemented by visualization services 4620 to generate higher quality visualizations. In at least one embodiment, visualizations may include, without limitation, 2D image renderings, 3D volume renderings, 3D volume reconstruction, 2D tomographic slices, virtual reality displays, augmented reality displays, etc. In at least one embodiment, virtualized environments may be used to generate a virtual interactive display or environment (e.g., a virtual environment) for interaction by users of a system (e.g., doctors, nurses, radiologists, etc.). In at least one embodiment, visualization services 4620 may include an internal visualizer, cinematics, and/or other rendering or image processing capabilities or functionality (e.g., ray tracing, rasterization, internal optics, etc.).

In at least one embodiment, hardware 4522 may include GPUs 4622, AI system 4624, cloud 4626, and/or any other hardware used for executing training system 4504 and/or deployment system 4506. In at least one embodiment, GPUs 4622 (e.g., NVIDIA's TESLA and/or QUADRO GPUs) may include any number of GPUs that may be used for executing processing tasks of compute services 4616, AI services 4618, visualization services 4620, other services, and/or any of features or functionality of software 4518. For example, with respect to AI services 4618, GPUs 4622 may be used to perform pre-processing on imaging data (or other data types used by machine learning models), post-processing on outputs of machine learning models, and/or to perform inferencing (e.g., to execute machine learning models). In at least one embodiment, cloud 4626, AI system 4624, and/or other components of system 4600 may use GPUs 4622. In at least one embodiment, cloud 4626 may include a GPU-optimized platform for deep learning tasks. In at least one embodiment, AI system 4624 may use GPUs, and cloud 4626—or at least a portion tasked with deep learning or inferencing—may be executed using one or more AI systems 4624. As such, although hardware 4522 is illustrated as discrete components, this is not intended to be limiting, and any components of hardware 4522 may be combined with, or leveraged by, any other components of hardware 4522.

In at least one embodiment, AI system 4624 may include a purpose-built computing system (e.g., a super-computer or an HPC) configured for inferencing, deep learning, machine learning, and/or other artificial intelligence tasks. In at least one embodiment, AI system 4624 (e.g., NVIDIA's DGX) may include GPU-optimized software (e.g., a software stack) that may be executed using a plurality of GPUs 4622, in addition to CPUs, RAM, storage, and/or other components, features, or functionality. In at least one embodiment, one or more AI systems 4624 may be implemented in cloud 4626 (e.g., in a data center) for performing some or all of AI-based processing tasks of system 4600.

In at least one embodiment, cloud 4626 may include a GPU-accelerated infrastructure (e.g., NVIDIA's NGC) that may provide a GPU-optimized platform for executing processing tasks of system 4600. In at least one embodiment, cloud 4626 may include an AI system(s) 4624 for performing one or more of AI-based tasks of system 4600 (e.g., as a hardware abstraction and scaling platform). In at least one embodiment, cloud 4626 may integrate with application orchestration system 4628 leveraging multiple GPUs to enable seamless scaling and load balancing between and among applications and services 4520. In at least one embodiment, cloud 4626 may tasked with executing at least some of services 4520 of system 4600, including compute services 4616, AI services 4618, and/or visualization services 4620, as described herein. In at least one embodiment, cloud 4626 may perform small and large batch inference (e.g., executing NVIDIA's TENSOR RT), provide an accelerated parallel computing API and platform 4630 (e.g., NVIDIA's CUDA), execute application orchestration system 4628 (e.g., KUBERNETES), provide a graphics rendering API and platform (e.g., for ray-tracing, 2D graphics, 3D graphics, and/or other rendering techniques to produce higher quality cinematics), and/or may provide other functionality for system 4600.

In at least one embodiment, in an effort to preserve patient confidentiality (e.g., where patient data or records are to be used off-premises), cloud 4626 may include a registry—such as a deep learning container registry. In at least one embodiment, a registry may store containers for instantiations of applications that may perform pre-processing, post-processing, or other processing tasks on patient data. In at least one embodiment, cloud 4626 may receive data that includes patient data as well as sensor data in containers, perform requested processing for just sensor data in those containers, and then forward a resultant output and/or visualizations to appropriate parties and/or devices (e.g., on-premises medical devices used for visualization or diagnoses), all without having to extract, store, or otherwise access patient data. In at least one embodiment, confidentiality of patient data is preserved in compliance with HIPAA and/or other data regulations.

FIG. 47 includes an example illustration of a deployment pipeline 4610A for processing imaging data, in accordance with at least one embodiment. In at least one embodiment, system 4600—and specifically deployment system 4506—may be used to customize, update, and/or integrate deployment pipeline(s) 4610A into one or more production environments. In at least one embodiment, deployment pipeline 4610A of FIG. 47 includes a non-limiting example of a deployment pipeline 4610A that may be custom defined by a particular user (or team of users) at a facility (e.g., at a hospital, clinic, lab, research environment, etc.). In at least one embodiment, to define deployment pipelines 4610A for a CT scanner 4702, a user may select—from a container registry, for example—one or more applications that perform specific functions or tasks with respect to imaging data generated by CT scanner 4702. In at least one embodiment, applications may be applied to deployment pipeline 4610A as containers that may leverage services 4520 and/or hardware 4522 of system 4600. In addition, deployment pipeline 4610A may include additional processing tasks or applications that may be implemented to prepare data for use by applications (e.g., DICOM adapter 4602B and DICOM reader 4706 may be used in deployment pipeline 4610A to prepare data for use by CT reconstruction 4708, organ segmentation 4710, etc.). In at least one embodiment, deployment pipeline 4610A may be customized or selected for consistent deployment, one time use, or for another frequency or interval. In at least one embodiment, a user may desire to have CT reconstruction 4708 and organ segmentation 4710 for several subjects over a specific interval, and thus may deploy pipeline 4610A for that period of time. In at least one embodiment, a user may select, for each request from system 4600, applications that a user wants to perform processing on that data for that request. In at least one embodiment, deployment pipeline 4610A may be adjusted at any interval and, because of adaptability and scalability of a container structure within system 4600, this may be a seamless process.

In at least one embodiment, deployment pipeline 4610A of FIG. 47 may include CT scanner 4702 generating imaging data of a patient or subject. In at least one embodiment, imaging data from CT scanner 4702 may be stored on a PACS server(s) 4704 associated with a facility housing CT scanner 4702. In at least one embodiment, PACS server(s) 4704 may include software and/or hardware components that may directly interface with imaging modalities (e.g., CT scanner 4702) at a facility. In at least one embodiment, DICOM adapter 4602B may enable sending and receipt of DICOM objects using DICOM protocols. In at least one embodiment, DICOM adapter 4602B may aid in preparation or configuration of DICOM data from PACS server(s) 4704 for use by deployment pipeline 4610A. In at least one embodiment, once DICOM data is processed through DICOM adapter 4602B, pipeline manager 4612 may route data through to deployment pipeline 4610A. In at least one embodiment, DICOM reader 4706 may extract image files and any associated metadata from DICOM data (e.g., raw sinogram data, as illustrated in visualization 4716A). In at least one embodiment, working files that are extracted may be stored in a cache for faster processing by other applications in deployment pipeline 4610A. In at least one embodiment, once DICOM reader 4706 has finished extracting and/or storing data, a signal of completion may be communicated to pipeline manager 4612. In at least one embodiment, pipeline manager 4612 may then initiate or call upon one or more other applications or containers in deployment pipeline 4610A.

In at least one embodiment, CT reconstruction 4708 application and/or container may be executed once data (e.g., raw sinogram data) is available for processing by CT reconstruction 4708 application. In at least one embodiment, CT reconstruction 4708 may read raw sinogram data from a cache, reconstruct an image file out of raw sinogram data (e.g., as illustrated in visualization 4716B), and store resulting image file in a cache. In at least one embodiment, at completion of reconstruction, pipeline manager 4612 may be signaled that reconstruction task is complete. In at least one embodiment, once reconstruction is complete, and a reconstructed image file may be stored in a cache (or other storage device), organ segmentation 4710 application and/or container may be triggered by pipeline manager 4612. In at least one embodiment, organ segmentation 4710 application and/or container may read an image file from a cache, normalize or convert an image file to format suitable for inference (e.g., convert an image file to an input resolution of a machine learning model), and run inference against a normalized image. In at least one embodiment, to run inference on a normalized image, organ segmentation 4710 application and/or container may rely on services 4520, and pipeline manager 4612 and/or application orchestration system 4628 may facilitate use of services 4520 by organ segmentation 4710 application and/or container. In at least one embodiment, for example, organ segmentation 4710 application and/or container may leverage AI services 4618 to perform inference on a normalized image, and AI services 4618 may leverage hardware 4522 (e.g., AI system 4624) to execute AI services 4618. In at least one embodiment, a result of an inference may be a mask file (e.g., as illustrated in visualization 4716C) that may be stored in a cache (or other storage device).

In at least one embodiment, once applications that process DICOM data and/or data extracted from DICOM data have completed processing, a signal may be generated for pipeline manager 4612. In at least one embodiment, pipeline manager 4612 may then execute DICOM writer 4712 to read results from a cache (or other storage device), package results into a DICOM format (e.g., as DICOM output 4714) for use by users at a facility who generated a request. In at least one embodiment, DICOM output 4714 may then be transmitted to DICOM adapter 4602B to prepare DICOM output 4714 for storage on PACS server(s) 4704 (e.g., for viewing by a DICOM viewer at a facility). In at least one embodiment, in response to a request for reconstruction and segmentation, visualizations 4716B and 4716C may be generated and available to a user for diagnoses, research, and/or for other purposes.

Although illustrated as consecutive application in deployment pipeline 4610A, CT reconstruction 4708 and organ segmentation 4710 applications may be processed in parallel in at least one embodiment. In at least one embodiment, where applications do not have dependencies on one another, and data is available for each application (e.g., after DICOM reader 4706 extracts data), applications may be executed at a same time, substantially at a same time, or with some overlap. In at least one embodiment, where two or more applications require similar services 4520, a scheduler of system 4600 may be used to load balance and distribute compute or processing resources between and among various applications. In at least one embodiment, in some embodiments, parallel computing platform 4630 may be used to perform parallel processing for applications to decrease run-time of deployment pipeline 4610A to provide real-time results.

In at least one embodiment, and with reference to FIGS. 48A-48B, deployment system 4506 may be implemented as one or more virtual instruments to perform different functionalities—such as image processing, segmentation, enhancement, AI, visualization, and inferencing—with imaging devices (e.g., CT scanners, X-ray machines, MRI machines, etc.), sequencing devices, genomics devices, and/or other device types. In at least one embodiment, system 4600 may allow for creation and provision of virtual instruments that may include a software-defined deployment pipeline 4610 that may receive raw/unprocessed input data generated by a device(s) and output processed/reconstructed data. In at least one embodiment, deployment pipelines 4610 (e.g., 4610A and 4610B) that represent virtual instruments may implement intelligence into a pipeline, such as by leveraging machine learning models, to provide containerized inference support to a system. In at least one embodiment, virtual instruments may execute any number of containers each including instantiations of applications. In at least one embodiment, such as where real-time processing is desired, deployment pipelines 4610 representing virtual instruments may be static (e.g., containers and/or applications may be set), while in other examples, container and/or applications for virtual instruments may be selected (e.g., on a per-request basis) from a pool of applications or resources (e.g., within a container registry).

In at least one embodiment, system 4600 may be instantiated or executed as one or more virtual instruments on-premise at a facility in, for example, a computing system deployed next to or otherwise in communication with a radiology machine, an imaging device, and/or another device type at a facility. In at least one embodiment, however, an on-premise installation may be instantiated or executed within a computing system of a device itself (e.g., a computing system integral to an imaging device), in a local datacenter (e.g., a datacenter on-premise), and/or in a cloud-environment (e.g., in cloud 4626). In at least one embodiment, deployment system 4506, operating as a virtual instrument, may be instantiated by a supercomputer or other HPC system in some examples. In at least one embodiment, on-premise installation may allow for high-bandwidth uses (via, for example, higher throughput local communication interfaces, such as RF over Ethernet) for real-time processing. In at least one embodiment, real-time or near real-time processing may be particularly useful where a virtual instrument supports an ultrasound device or other imaging modality where immediate visualizations are expected or required for accurate diagnoses and analyses. In at least one embodiment, a cloud-computing architecture may be capable of dynamic bursting to a cloud computing service provider, or other compute cluster, when local demand exceeds on-premise capacity or capability. In at least one embodiment, a cloud architecture, when implemented, may be tuned for training neural networks or other machine learning models, as described herein with respect to training system 4504. In at least one embodiment, with training pipelines in place, machine learning models may be continuously learn and improve as they process additional data from devices they support. In at least one embodiment, virtual instruments may be continually improved using additional data, new data, existing machine learning models, and/or new or updated machine learning models.

In at least one embodiment, a computing system may include some or all of hardware 4522 described herein, and hardware 4522 may be distributed in any of a number of ways including within a device, as part of a computing device coupled to and located proximate a device, in a local datacenter at a facility, and/or in cloud 4626. In at least one embodiment, because deployment system 4506 and associated applications or containers are created in software (e.g., as discrete containerized instantiations of applications), behavior, operation, and configuration of virtual instruments, as well as outputs generated by virtual instruments, may be modified or customized as desired, without having to change or alter raw output of a device that a virtual instrument supports. Imaging systems as described here can be used as depth cameras to determine a robotic grasp. For example, techniques described herein can be used to conduct robotic surgery by using the imaging techniques to produce a point cloud of a human organ or foreign body, which can then be grasped using a robotic gripper, or manipulated in other ways with a robotic manipulator.

FIG. 48A includes an example data flow diagram of a virtual instrument supporting an ultrasound device, in accordance with at least one embodiment. In at least one embodiment, deployment pipeline 4610B may leverage one or more of services 4520 of system 4600. In at least one embodiment, deployment pipeline 4610B and services 4520 may leverage hardware 4522 of a system either locally or in cloud 4626. In at least one embodiment, although not illustrated, process 4800 may be facilitated by pipeline manager 4612, application orchestration system 4628, and/or parallel computing platform 4630.

In at least one embodiment, process 4800 may include receipt of imaging data from an ultrasound device 4802. In at least one embodiment, imaging data may be stored on PACS server(s) in a DICOM format (or other format, such as RIS, CIS, REST compliant, RPC, raw, etc.), and may be received by system 4600 for processing through deployment pipeline 4610 selected or customized as a virtual instrument (e.g., a virtual ultrasound) for ultrasound device 4802. In at least one embodiment, imaging data may be received directly from an imaging device (e.g., ultrasound device 4802) and processed by a virtual instrument. In at least one embodiment, a transducer or other signal converter communicatively coupled between an imaging device and a virtual instrument may convert signal data generated by an imaging device to image data that may be processed by a virtual instrument. In at least one embodiment, raw data and/or image data may be applied to DICOM reader 4706 to extract data for use by applications or containers of deployment pipeline 4610B. In at least one embodiment, DICOM reader 4706 may leverage data augmentation library 4814 (e.g., NVIDIA's DALI) as a service 4520 (e.g., as one of compute service(s) 4616) for extracting, resizing, rescaling, and/or otherwise preparing data for use by applications or containers.

In at least one embodiment, once data is prepared, a reconstruction 4806 application and/or container may be executed to reconstruct data from ultrasound device 4802 into an image file. In at least one embodiment, after reconstruction 4806, or at a same time as reconstruction 4806, a detection 4808 application and/or container may be executed for anomaly detection, object detection, feature detection, and/or other detection tasks related to data. In at least one embodiment, an image file generated during reconstruction 4806 may be used during detection 4808 to identify anomalies, objects, features, etc. In at least one embodiment, detection 4808 application may leverage an inference engine 4816 (e.g., as one of AI service(s) 4618) to perform inference on data to generate detections. In at least one embodiment, one or more machine learning models (e.g., from training system 4504) may be executed or called by detection 4808 application.

In at least one embodiment, once reconstruction 4806 and/or detection 4808 is/are complete, data output from these application and/or containers may be used to generate visualizations 4810, such as visualization 4812 (e.g., a grayscale output) displayed on a workstation or display terminal. In at least one embodiment, visualization may allow a technician or other user to visualize results of deployment pipeline 4610B with respect to ultrasound device 4802. In at least one embodiment, visualization 4810 may be executed by leveraging a render component 4818 of system 4600 (e.g., one of visualization service(s) 4620). In at least one embodiment, render component 4818 may execute a 2D, OpenGL, or ray-tracing service to generate visualization 4812.

FIG. 48B includes an example data flow diagram of a virtual instrument supporting a CT scanner, in accordance with at least one embodiment. In at least one embodiment, deployment pipeline 4610C may leverage one or more of services 4520 of system 4600. In at least one embodiment, deployment pipeline 4610C and services 4520 may leverage hardware 4522 of a system either locally or in cloud 4626. In at least one embodiment, although not illustrated, process 4820 may be facilitated by pipeline manager 4612, application orchestration system 4628, and/or parallel computing platform 4630.

In at least one embodiment, process 4820 may include CT scanner 4822 generating raw data that may be received by DICOM reader 4706 (e.g., directly, via a PACS server 4704, after processing, etc.). In at least one embodiment, a Virtual CT (instantiated by deployment pipeline 4610C) may include a first, real-time pipeline for monitoring a patient (e.g., patient movement detection AI 4826) and/or for adjusting or optimizing exposure of CT scanner 4822 (e.g., using exposure control AI 4824). In at least one embodiment, one or more of applications (e.g., 4824 and 4826) may leverage a service 4520, such as AI service(s) 4618. In at least one embodiment, outputs of exposure control AI 4824 application (or container) and/or patient movement detection AI 4826 application (or container) may be used as feedback to CT scanner 4822 and/or a technician for adjusting exposure (or other settings of CT scanner 4822) and/or informing a patient to move less.

In at least one embodiment, deployment pipeline 4610C may include a non-real-time pipeline for analyzing data generated by CT scanner 4822. In at least one embodiment, a second pipeline may include CT reconstruction 4708 application and/or container, a coarse detection AI 4828 application and/or container, a fine detection AI 4832 application and/or container (e.g., where certain results are detected by coarse detection AI 4828), a visualization 4830 application and/or container, and a DICOM writer 4712 (and/or other data type writer, such as RIS, CIS, REST compliant, RPC, raw, etc.) application and/or container. In at least one embodiment, raw data generated by CT scanner 4822 may be passed through pipelines of deployment pipeline 4610C (instantiated as a virtual CT instrument) to generate results. In at least one embodiment, results from DICOM writer 4712 may be transmitted for display and/or may be stored on PACS server(s) 4704 for later retrieval, analysis, or display by a technician, practitioner, or other user.

FIG. 49A illustrates a data flow diagram for a process 4900 to train, retrain, or update a machine learning model, in accordance with at least one embodiment. In at least one embodiment, process 4900 may be executed using, as a non-limiting example, system 4600 of FIG. 46 . In at least one embodiment, process 4900 may leverage services 4520 and/or hardware 4522 of system 4600, as described herein. In at least one embodiment, refined models 4912 generated by process 4900 may be executed by deployment system 4506 for one or more containerized applications in deployment pipelines 4610.

In at least one embodiment, model training 4514 may include retraining or updating an initial model 4904 (e.g., a pre-trained model) using new training data (e.g., new input data, such as customer dataset 4906, and/or new ground truth data associated with input data). In at least one embodiment, to retrain, or update, initial model 4904, output or loss layer(s) of initial model 4904 may be reset, or deleted, and/or replaced with an updated or new output or loss layer(s). In at least one embodiment, initial model 4904 may have previously fine-tuned parameters (e.g., weights and/or biases) that remain from prior training, so training or retraining 4514 may not take as long or require as much processing as training a model from scratch. In at least one embodiment, during model training 4514, by having reset or replaced output or loss layer(s) of initial model 4904, parameters may be updated and re-tuned for a new data set based on loss calculations associated with accuracy of output or loss layer(s) at generating predictions on new, customer dataset 4906 (e.g., image data 4508 of FIG. 45 ).

In at least one embodiment, pre-trained models 4606 may be stored in a data store, or registry (e.g., model registry 4524 of FIG. 45 ). In at least one embodiment, pre-trained models 4606 may have been trained, at least in part, at one or more facilities other than a facility executing process 4900. In at least one embodiment, to protect privacy and rights of patients, subjects, or clients of different facilities, pre-trained models 4606 may have been trained, on-premise, using customer or patient data generated on-premise. In at least one embodiment, pre-trained models 4606 may be trained using cloud 4626 and/or other hardware 4522, but confidential, privacy protected patient data may not be transferred to, used by, or accessible to any components of cloud 4626 (or other off premise hardware). In at least one embodiment, where a pre-trained model 4606 is trained at using patient data from more than one facility, pre-trained model 4606 may have been individually trained for each facility prior to being trained on patient or customer data from another facility. In at least one embodiment, such as where a customer or patient data has been released of privacy concerns (e.g., by waiver, for experimental use, etc.), or where a customer or patient data is included in a public data set, a customer or patient data from any number of facilities may be used to train pre-trained model 4606 on-premise and/or off premise, such as in a datacenter or other cloud computing infrastructure.

In at least one embodiment, when selecting applications for use in deployment pipelines 4610, a user may also select machine learning models to be used for specific applications. In at least one embodiment, a user may not have a model for use, so a user may select a pre-trained model 4606 to use with an application. In at least one embodiment, pre-trained model 4606 may not be optimized for generating accurate results on customer dataset 4906 of a facility of a user (e.g., based on patient diversity, demographics, types of medical imaging devices used, etc.). In at least one embodiment, prior to deploying pre-trained model 4606 into deployment pipeline 4610 for use with an application(s), pre-trained model 4606 may be updated, retrained, and/or fine-tuned for use at a respective facility.

In at least one embodiment, a user may select pre-trained model 4606 that is to be updated, retrained, and/or fine-tuned, and pre-trained model 4606 may be referred to as initial model 4904 for training system 4504 within process 4900. In at least one embodiment, customer dataset 4906 (e.g., imaging data, genomics data, sequencing data, or other data types generated by devices at a facility) may be used to perform model training 4514 (which may include, without limitation, transfer learning) on initial model 4904 to generate refined model 4912. In at least one embodiment, ground truth data corresponding to customer dataset 4906 may be generated by training system 4504. In at least one embodiment, ground truth data may be generated, at least in part, by clinicians, scientists, doctors, practitioners, at a facility (e.g., as labeled clinic data 4512 of FIG. 45 ).

In at least one embodiment, AI-assisted annotation 4510 may be used in some examples to generate ground truth data. In at least one embodiment, AI-assisted annotation 4510 (e.g., implemented using an AI-assisted annotation SDK) may leverage machine learning models (e.g., neural networks) to generate suggested or predicted ground truth data for a customer dataset. In at least one embodiment, user 4910 may use annotation tools within a user interface (a graphical user interface (GUI)) on computing device 4908.

In at least one embodiment, user 4910 may interact with a GUI via computing device 4908 to edit or fine-tune annotations or auto-annotations. In at least one embodiment, a polygon editing feature may be used to move vertices of a polygon to more accurate or fine-tuned locations.

In at least one embodiment, once customer dataset 4906 has associated ground truth data, ground truth data (e.g., from AI-assisted annotation, manual labeling, etc.) may be used by during model training 4514 to generate refined model 4912. In at least one embodiment, customer dataset 4906 may be applied to initial model 4904 any number of times, and ground truth data may be used to update parameters of initial model 4904 until an acceptable level of accuracy is attained for refined model 4912. In at least one embodiment, once refined model 4912 is generated, refined model 4912 may be deployed within one or more deployment pipelines 4610 at a facility for performing one or more processing tasks with respect to medical imaging data.

In at least one embodiment, refined model 4912 may be uploaded to pre-trained models 4606 in model registry 4524 to be selected by another facility. In at least one embodiment, his process may be completed at any number of facilities such that refined model 4912 may be further refined on new datasets any number of times to generate a more universal model.

Models trained to perform the operation of robotic grasp evaluation and refinement may, in various examples, utilize the techniques described above.

FIG. 49B is an example illustration of a client-server architecture 4932 to enhance annotation tools with pre-trained annotation models, in accordance with at least one embodiment. In at least one embodiment, AI-assisted annotation tools 4936 may be instantiated based on a client-server architecture 4932. In at least one embodiment, annotation tools 4936 in imaging applications may aid radiologists, for example, identify organs and abnormalities. In at least one embodiment, imaging applications may include software tools that help user 4910 to identify, as a non-limiting example, a few extreme points on a particular organ of interest in raw images 4934 (e.g., in a 3D MRI or CT scan) and receive auto-annotated results for all 2D slices of a particular organ. In at least one embodiment, results may be stored in a data store as training data 4938 and used as (for example and without limitation) ground truth data for training. In at least one embodiment, when computing device 4908 sends extreme points for AI-assisted annotation 4510, a deep learning model, for example, may receive this data as input and return inference results of a segmented organ or abnormality. In at least one embodiment, pre-instantiated annotation tools, such as AI-Assisted Annotation Tool 4936B in FIG. 49B, may be enhanced by making API calls (e.g., API Call 4944) to a server, such as an Annotation Assistant Server 4940 that may include a set of pre-trained models 4942 stored in an annotation model registry, for example. In at least one embodiment, an annotation model registry may store pre-trained models 4942 (e.g., machine learning models, such as deep learning models) that are pre-trained to perform AI-assisted annotation on a particular organ or abnormality. In at least one embodiment, these models may be further updated by using training pipelines 4604. In at least one embodiment, pre-installed annotation tools may be improved over time as new labeled clinic data 4512 is added.

Inference and/or training logic 1615 are used to perform inferencing and/or training operations associated with one or more embodiments. Details regarding inference and/or training logic 1615 are provided herein in conjunction with FIGS. 16A and/or 16B.

At least one embodiment of the disclosure can be described in view of the following clauses:

1. A computer system comprising one or more processors and computer-readable memory storing executable instructions that, as a result of being executed by the one or more processors, cause the computer system to at least: obtain a three dimensional point cloud of an object; use a first neural network, generate, from the three dimensional point cloud, a set of grasp poses that allow a robot to grasp the object; use a second neural network to determine an evaluation of individual grasps in the set of grasp poses; and refine the individual grasps in the set of grasp poses based at least in part on a gradient of the evaluation determined by the second neural network to produce a set of refined grasp poses.

2. The computer system of clause 1, wherein the executable instructions, as a result of being executed by the one or more processors, further cause the computer system to: select a particular grasp pose from the set of refined grasp poses based at least in part on the evaluation of individual grasps in the set of grasp poses; and cause a the robot to grasp the object by performing the particular grasp pose using the robot.

3. The computer system of clause 1 or 2, wherein the executable instructions, as a result of being executed by the one or more processors, further cause the computer system to: obtain three dimensional image information from a depth camera; and generate, from the three dimensional image information, the three dimensional point cloud of the object.

4. The computer system of any of clauses 1 to 3, wherein the executable instructions, as a result of being executed by the one or more processors, further cause the computer system to refine a previously refined grasp pose based at least in part on a gradient of the previously refined grasp pose determined by the second neural network.

5. The computer system of any of clauses 1 to 4, wherein the first neural network is a variational autoencoder trained so as to map a partial point cloud of the object to the set of grasp poses for the object.

6. The computer system of any of clauses 1 to 5, wherein refining each grasp is accomplished at least in part by enforcing a rigidity constraint on a gripper of the robot.

7. The computer system of any of clauses 1 to 6, wherein the second neural network uses the three dimensional point cloud of the object to evaluate each grasp pose in the set of grasp poses.

8. The computer system of any of clauses 1 to 7, wherein the three dimensional point cloud of the object is a point cloud of a portion of the object.

9. A computer-implemented method comprising: generating a three dimensional point cloud of an object using image data produced by a depth camera; providing the three dimensional point cloud to a first neural network, the first neural network trained so as to produce a first set of grasp poses from the three dimensional point cloud that allow a robot to grasp the object; providing the first set of grasp poses and the three dimensional point cloud to a second neural network, the second neural network trained so as to determine an evaluation of individual grasp poses; and modifying the first set of grasp poses using a gradient produced by the second neural network to produce a second set of grasp poses.

10. The computer-implemented method of clause 9, further comprising: identifying a third set of grasp poses from the second set of grasp poses where individual grasp poses have an associated evaluation greater than a threshold value; and selecting a particular grasp pose from the third set of grasp poses based at least in part on the evaluation of individual grasps in the third set of grasp poses; and grasping the object by performing the particular grasp pose using the robot.

11. The computer-implemented method of clause 9 or 10, further comprising: obtaining image information of the object, the image information including depth information for at least part of the object; and determining a three dimensional point cloud of at least part of the object from the image information.

12. The computer-implemented method of any of clauses 9 to 11, further comprising producing a third set of grasp poses by modifying the second set of grasp poses based at least in part on a gradient produced by the second neural network for the second set of grasp poses.

13. The computer-implemented method of any of clauses 9 to 12, wherein: the first neural network is trained so as to map a partial point cloud of the object to the first set of grasp poses for the object; and the second neural network is trained so as to produce an evaluation of a chance of success for a grasp pose of the object.

14. The computer-implemented method of any of clauses 9 to 13, wherein the modification of an individual grasp pose is limited to less than a translation update amount.

15. The computer-implemented method of any of clauses 9 to 14, wherein the second neural network represents a differentiable function of grasp success that is based at least in part on the point cloud of the object and a grasp pose of the object.

16. The computer-implemented method of any of clauses 9 to 15, wherein the second neural network evaluates a grasp pose by at least extrapolating a position of a portion of the object that is not represented by the point cloud.

17. A machine-readable medium having stored thereon a set of instructions, which if performed by one or more processors, cause the one or more processors to at least: use a first neural network to generate, from a three dimensional point cloud of an object, a set of grasp poses for grasping the object with a gripper of a robot; use a second neural network to determine an evaluation of individual grasps in the set of grasp poses; and improve a probability of success for the individual grasps in the set of grasp poses based at least in part on a gradient of the evaluation to produce a set of improved grasp poses.

18. The machine-readable medium of clause 17, wherein the set of instructions, as a result of being executed by the one or more processors, further cause the one or more processors to: exclude, from the set of improved grasp poses, poses predicted to be unsuccessful based at least in part on the evaluation; and cause the robot to grasp the object by performing a particular grasp pose selected from the set of improved grasp poses.

19. The machine-readable medium of clause 17 or 18, wherein the three dimensional point cloud of the object is generated using a medical imaging device.

20. The machine-readable medium of any of clauses 17 to 19, wherein the set of instructions, as a result of being executed by the one or more processors, further cause the one or more processors to improve an individual grasp pose in the set of improved grasp poses using a gradient of the individual grasp pose generated by the second neural network.

21. The machine-readable medium of any of clauses 17 to 20, wherein the first neural network is a variational autoencoder trained so as to map a partial point cloud of the object to the set of grasp poses for the object.

22. The machine-readable medium of any of clauses 17 to 21, wherein the second neural network is trained with both successful and unsuccessful grasps.

23. The machine-readable medium of any of clauses 17 to 22, wherein the second neural network uses the three dimensional point cloud of the object and an individual grasp pose in the set of grasp poses to evaluate a chance of success for the individual grasp pose.

24. A robot comprising: one or more processors and memory storing executable instructions that, as a result of being executed by the one or more processors, cause the robot to implement: a first neural network trained so as to generate a set of grasp poses for an object from a point cloud of the object; a second neural network trained so as to evaluate success for individual grasp poses of the set of grasp poses; and a robotic manipulator that executes a refined grasp pose generated by refining a grasp pose from the set of grasp poses with a gradient produced by the second neural network.

25. The robot of clause 24 wherein the point cloud is generated using image information collected from a medical imaging device.

26. The robot of clause 25 wherein the medical imaging device is a computed tomography (CT) scanner, a magnetic resonance imaging machine, an x-ray imaging machine, or an ultrasound machine.

27. The robot of any of clauses 24 to 26 wherein the robotic manipulator comprises at least one of a scalpel, a gripper, a needle, a scissors, a laser, or a clamp.

In at least one embodiment, a single semiconductor platform may refer to a sole unitary semiconductor-based integrated circuit or chip. In at least one embodiment, multi-chip modules may be used with increased connectivity which simulate on-chip operation, and make substantial improvements over utilizing a conventional central processing unit (“CPU”) and bus implementation. In at least one embodiment, various modules may also be situated separately or in various combinations of semiconductor platforms per desires of user.

In at least one embodiment, referring back to FIG. 22 , computer programs in form of machine-readable executable code or computer control logic algorithms are stored in main memory 2204 and/or secondary storage. Computer programs, if executed by one or more processors, enable system 2200 to perform various functions in accordance with at least one embodiment. In at least one embodiment, memory 2204, storage, and/or any other storage are possible examples of computer-readable media. In at least one embodiment, secondary storage may refer to any suitable storage device or system such as a hard disk drive and/or a removable storage drive, representing a floppy disk drive, a magnetic tape drive, a compact disk drive, digital versatile disk (“DVD”) drive, recording device, universal serial bus (“USB”) flash memory, etc. In at least one embodiment, architecture and/or functionality of various previous figures are implemented in context of CPU 2202, parallel processing system 2212, an integrated circuit capable of at least a portion of capabilities of both CPU 2202, parallel processing system 2212, a chipset (e.g., a group of integrated circuits designed to work and sold as a unit for performing related functions, etc.), and/or any suitable combination of integrated circuit(s).

In at least one embodiment, architecture and/or functionality of various previous figures are implemented in context of a general computer system, a circuit board system, a game console system dedicated for entertainment purposes, an application-specific system, and more. In at least one embodiment, computer system 2200 may take form of a desktop computer, a laptop computer, a tablet computer, servers, supercomputers, a smart-phone (e.g., a wireless, hand-held device), personal digital assistant (“PDA”), a digital camera, a vehicle, a head mounted display, a hand-held electronic device, a mobile phone device, a television, workstation, game consoles, embedded system, and/or any other type of logic.

In at least one embodiment, parallel processing system 2212 includes, without limitation, a plurality of parallel processing units (“PPUs”) 2214 and associated memories 2216. In at least one embodiment, PPUs 2214 are connected to a host processor or other peripheral devices via an interconnect 2218 and a switch 2220 or multiplexer. In at least one embodiment, parallel processing system 2212 distributes computational tasks across PPUs 2214 which can be parallelizable—for example, as part of distribution of computational tasks across multiple graphics processing unit (“GPU”) thread blocks. In at least one embodiment, memory is shared and accessible (e.g., for read and/or write access) across some or all of PPUs 2214, although such shared memory may incur performance penalties relative to use of local memory and registers resident to a PPU 2214. In at least one embodiment, operation of PPUs 2214 is synchronized through use of a command such as _syncthreads( ), wherein all threads in a block (e.g., executed across multiple PPUs 2214) to reach a certain point of execution of code before proceeding.

Other variations are within spirit of present disclosure. Thus, while disclosed techniques are susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in drawings and have been described above in detail. It should be understood, however, that there is no intention to limit disclosure to specific form or forms disclosed, but on contrary, intention is to cover all modifications, alternative constructions, and equivalents falling within spirit and scope of disclosure, as defined in appended claims.

Use of terms “a” and “an” and “the” and similar referents in context of describing disclosed embodiments (especially in context of following claims) are to be construed to cover both singular and plural, unless otherwise indicated herein or clearly contradicted by context, and not as a definition of a term. Terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms (meaning “including, but not limited to,”) unless otherwise noted. “Connected,” when unmodified and referring to physical connections, is to be construed as partly or wholly contained within, attached to, or joined together, even if there is something intervening. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within range, unless otherwise indicated herein and each separate value is incorporated into specification as if it were individually recited herein. In at least one embodiment, use of term “set” (e.g., “a set of items”) or “subset” unless otherwise noted or contradicted by context, is to be construed as a nonempty collection comprising one or more members. Further, unless otherwise noted or contradicted by context, term “subset” of a corresponding set does not necessarily denote a proper subset of corresponding set, but subset and corresponding set may be equal.

Conjunctive language, such as phrases of form “at least one of A, B, and C,” or “at least one of A, B and C,” unless specifically stated otherwise or otherwise clearly contradicted by context, is otherwise understood with context as used in general to present that an item, term, etc., may be either A or B or C, or any nonempty subset of set of A and B and C. For instance, in illustrative example of a set having three members, conjunctive phrases “at least one of A, B, and C” and “at least one of A, B and C” refer to any of following sets: {A}, {B}, {C}, {A, B}, {A, C}, {B, C}, {A, B, C}. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of A, at least one of B and at least one of C each to be present. In addition, unless otherwise noted or contradicted by context, term “plurality” indicates a state of being plural (e.g., “a plurality of items” indicates multiple items). In at least one embodiment, number of items in a plurality is at least two, but can be more when so indicated either explicitly or by context. Further, unless stated otherwise or otherwise clear from context, phrase “based on” means “based at least in part on” and not “based solely on.”

Operations of processes described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. In at least one embodiment, a process such as those processes described herein (or variations and/or combinations thereof) is performed under control of one or more computer systems configured with executable instructions and is implemented as code (e.g., executable instructions, one or more computer programs or one or more applications) executing collectively on one or more processors, by hardware or combinations thereof. In at least one embodiment, code is stored on a computer-readable storage medium, for example, in form of a computer program comprising a plurality of instructions executable by one or more processors. In at least one embodiment, a computer-readable storage medium is a non-transitory computer-readable storage medium that excludes transitory signals (e.g., a propagating transient electric or electromagnetic transmission) but includes non-transitory data storage circuitry (e.g., buffers, cache, and queues) within transceivers of transitory signals. In at least one embodiment, code (e.g., executable code or source code) is stored on a set of one or more non-transitory computer-readable storage media having stored thereon executable instructions (or other memory to store executable instructions) that, when executed (i.e., as a result of being executed) by one or more processors of a computer system, cause computer system to perform operations described herein. In at least one embodiment, set of non-transitory computer-readable storage media comprises multiple non-transitory computer-readable storage media and one or more of individual non-transitory storage media of multiple non-transitory computer-readable storage media lack all of code while multiple non-transitory computer-readable storage media collectively store all of code. In at least one embodiment, executable instructions are executed such that different instructions are executed by different processors—for example, a non-transitory computer-readable storage medium store instructions and a main central processing unit (“CPU”) executes some of instructions while a graphics processing unit (“GPU”) executes other instructions. In at least one embodiment, different components of a computer system have separate processors and different processors execute different subsets of instructions.

Accordingly, in at least one embodiment, computer systems are configured to implement one or more services that singly or collectively perform operations of processes described herein and such computer systems are configured with applicable hardware and/or software that enable performance of operations. Further, a computer system that implements at least one embodiment of present disclosure is a single device and, in another embodiment, is a distributed computer system comprising multiple devices that operate differently such that distributed computer system performs operations described herein and such that a single device does not perform all operations.

Use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate embodiments of disclosure and does not pose a limitation on scope of disclosure unless otherwise claimed. No language in specification should be construed as indicating any non-claimed element as essential to practice of disclosure.

All references, including publications, patent applications, and patents, cited herein are hereby incorporated by reference to same extent as if each reference were individually and specifically indicated to be incorporated by reference and were set forth in its entirety herein.

In description and claims, terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms may be not intended as synonyms for each other. Rather, in particular examples, “connected” or “coupled” may be used to indicate that two or more elements are in direct or indirect physical or electrical contact with each other. “Coupled” may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

Unless specifically stated otherwise, it may be appreciated that throughout specification terms such as “processing,” “computing,” “calculating,” “determining,” or like, refer to action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within computing system's registers and/or memories into other data similarly represented as physical quantities within computing system's memories, registers or other such information storage, transmission or display devices.

In a similar manner, term “processor” may refer to any device or portion of a device that processes electronic data from registers and/or memory and transform that electronic data into other electronic data that may be stored in registers and/or memory. As non-limiting examples, “processor” may be a CPU or a GPU. A “computing platform” may comprise one or more processors. As used herein, “software” processes may include, for example, software and/or hardware entities that perform work over time, such as tasks, threads, and intelligent agents. Also, each process may refer to multiple processes, for carrying out instructions in sequence or in parallel, continuously or intermittently. In at least one embodiment, terms “system” and “method” are used herein interchangeably insofar as system may embody one or more methods and methods may be considered a system.

In present document, references may be made to obtaining, acquiring, receiving, or inputting analog or digital data into a subsystem, computer system, or computer-implemented machine. In at least one embodiment, process of obtaining, acquiring, receiving, or inputting analog and digital data can be accomplished in a variety of ways such as by receiving data as a parameter of a function call or a call to an application programming interface. In some implementations, process of obtaining, acquiring, receiving, or inputting analog or digital data can be accomplished by transferring data via a serial or parallel interface. In another implementation, process of obtaining, acquiring, receiving, or inputting analog or digital data can be accomplished by transferring data via a computer network from providing entity to acquiring entity. References may also be made to providing, outputting, transmitting, sending, or presenting analog or digital data. In various examples, process of providing, outputting, transmitting, sending, or presenting analog or digital data can be accomplished by transferring data as an input or output parameter of a function call, a parameter of an application programming interface or interprocess communication mechanism.

Although discussion above sets forth example implementations of described techniques, other architectures may be used to implement described functionality, and are intended to be within scope of this disclosure. Furthermore, although specific distributions of responsibilities are defined above for purposes of discussion, various functions and responsibilities might be distributed and divided in different ways, depending on circumstances.

Furthermore, although subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that subject matter claimed in appended claims is not necessarily limited to specific features or acts described. Rather, specific features and acts are disclosed as exemplary forms of implementing the claims. 

What is claimed is:
 1. A computer system comprising one or more processors and computer-readable memory storing executable instructions that, as a result of being executed by the one or more processors, cause the computer system to at least: use a first neural network to generate, from a three dimensional point cloud of an object, a set of grasp poses that allow a robot to grasp the object; use a second neural network to determine an evaluation of individual grasps in the set of grasp poses; and refine the individual grasps in the set of grasp poses based at least in part on a gradient of the evaluation determined by the second neural network to produce a set of refined grasp poses.
 2. The computer system of claim 1, wherein the executable instructions, as a result of being executed by the one or more processors, further cause the computer system to: select a particular grasp pose from the set of refined grasp poses based at least in part on the evaluation of individual grasps in the set of grasp poses; and cause a the robot to grasp the object by performing the particular grasp pose using the robot.
 3. The computer system of claim 1, wherein the executable instructions, as a result of being executed by the one or more processors, further cause the computer system to: obtain three dimensional image information from a depth camera; and generate, from the three dimensional image information, the three dimensional point cloud of the object.
 4. The computer system of claim 1, wherein the executable instructions, as a result of being executed by the one or more processors, further cause the computer system to refine a previously refined grasp pose based at least in part on a gradient of the previously refined grasp pose determined by the second neural network.
 5. The computer system of claim 1, wherein the first neural network is a variational autoencoder trained so as to map a partial point cloud of the object to the set of grasp poses for the object.
 6. The computer system of claim 1, wherein refining each grasp is accomplished at least in part by enforcing a rigidity constraint on a gripper of the robot.
 7. The computer system of claim 1, wherein the second neural network uses the three dimensional point cloud of the object to evaluate each grasp pose in the set of grasp poses.
 8. The computer system of claim 1, wherein the three dimensional point cloud of the object is a point cloud of a portion of the object.
 9. A computer-implemented method comprising: generating a three dimensional point cloud of an object using image data produced by a depth camera; providing the three dimensional point cloud to a first neural network, the first neural network trained so as to produce a first set of grasp poses from the three dimensional point cloud that allow a robot to grasp the object; providing the first set of grasp poses and the three dimensional point cloud to a second neural network, the second neural network trained so as to determine an evaluation of individual grasp poses; and modifying the first set of grasp poses using a gradient of the evaluation produced by the second neural network to produce a second set of grasp poses.
 10. The computer-implemented method of claim 9, further comprising: identifying a third set of grasp poses from the second set of grasp poses where individual grasp poses have an associated evaluation greater than a threshold value; and selecting a particular grasp pose from the third set of grasp poses based at least in part on the evaluation of individual grasps in the third set of grasp poses; and grasping the object by performing the particular grasp pose using the robot.
 11. The computer-implemented method of claim 9, further comprising: obtaining image information of the object, the image information including depth information for at least part of the object; and determining a three dimensional point cloud of at least part of the object from the image information.
 12. The computer-implemented method of claim 9, further comprising producing a third set of grasp poses by modifying the second set of grasp poses based at least in part on a gradient produced by the second neural network for the second set of grasp poses.
 13. The computer-implemented method of claim 9, wherein: the first neural network is trained so as to map a partial point cloud of the object to the first set of grasp poses for the object; and the second neural network is trained so as to produce an evaluation of a chance of success for a grasp pose of the object.
 14. The computer-implemented method of claim 9, wherein the modification of an individual grasp pose is limited to less than a translation update amount.
 15. The computer-implemented method of claim 9, wherein the second neural network represents a differentiable function of grasp success that is based at least in part on the point cloud of the object and a grasp pose of the object.
 16. The computer-implemented method of claim 9, wherein the second neural network evaluates a grasp pose by at least extrapolating a position of a portion of the object that is not represented by the point cloud.
 17. A non-transitory machine-readable medium having stored thereon a set of instructions, which if performed by one or more processors, cause the one or more processors to at least: use a first neural network to generate, from a three dimensional point cloud of an object, a set of grasp poses for grasping the object with a gripper of a robot; use a second neural network to determine an evaluation of individual grasps in the set of grasp poses; and improve a probability of success for the individual grasps in the set of grasp poses based at least in part on a gradient of the evaluation to produce a set of improved grasp poses.
 18. The non-transitory machine-readable medium of claim 17, wherein the set of instructions, as a result of being executed by the one or more processors, further cause the one or more processors to: exclude, from the set of improved grasp poses, poses predicted to be unsuccessful based at least in part on the evaluation; and cause the robot to grasp the object by performing a particular grasp pose selected from the set of improved grasp poses.
 19. The non-transitory machine-readable medium of claim 17, wherein the three dimensional point cloud of the object is generated using a medical imaging device.
 20. The non-transitory machine-readable medium of claim 17, wherein the set of instructions, as a result of being executed by the one or more processors, further cause the one or more processors to improve an individual grasp pose in the set of improved grasp poses using a gradient of the individual grasp pose generated by the second neural network.
 21. The non-transitory machine-readable medium of claim 17, wherein the first neural network is a variational autoencoder trained so as to map a partial point cloud of the object to the set of grasp poses for the object.
 22. The non-transitory machine-readable medium of claim 17, wherein the second neural network is trained with both successful and unsuccessful grasps.
 23. The non-transitory machine-readable medium of claim 17, wherein the second neural network uses the three dimensional point cloud of the object and an individual grasp pose in the set of grasp poses to evaluate a chance of success for the individual grasp pose.
 24. A robot comprising: one or more processors and memory storing executable instructions that, as a result of being executed by the one or more processors, cause the robot to implement: a first neural network trained so as to generate a set of grasp poses for an object from a point cloud of the object; a second neural network trained so as to evaluate success for individual grasp poses of the set of grasp poses; and a robotic manipulator that executes a refined grasp pose generated by refining a grasp pose from the set of grasp poses with a gradient produced by the second neural network.
 25. The robot of claim 24 wherein the point cloud is generated using image information collected from a medical imaging device.
 26. The robot of claim 25 wherein the medical imaging device is a computed tomography (CT) scanner, a magnetic resonance imaging machine, an x-ray imaging machine, or an ultrasound machine.
 27. The robot of claim 24 wherein the robotic manipulator comprises at least one of a scalpel, a gripper, a needle, a scissors, a laser, or a clamp. 